coredump.conf, coredump.conf.d — Core dump storage configuration files
These files configure the behavior of
a handler for core dumps invoked by the kernel. Whether systemd-coredump is used
is determined by the kernel's
pages for the details.
The default configuration is defined during compilation, so a
configuration file is only needed when it is necessary to deviate
from those defaults. By default, the configuration file in
/etc/systemd/ contains commented out entries
showing the defaults as a guide to the administrator. This file
can be edited to create local overrides.
When packages need to customize the configuration, they can
install configuration snippets in
/usr/lib/systemd/*.conf.d/. Files in
/etc/ are reserved for the local
administrator, who may use this logic to override the
configuration files installed by vendor packages. The main
configuration file is read before any of the configuration
directories, and has the lowest precedence; entries in a file in
any configuration directory override entries in the single
configuration file. Files in the
configuration subdirectories are sorted by their filename in lexicographic
order, regardless of which of the subdirectories they reside in. When
multiple files specify the same option, for options which accept just a
single value, the entry in the file with the lexicographically latest name
takes precedence. For options which accept a list of values, entries are
collected as they occur in files sorted lexicographically. It is recommended
to prefix all filenames in those subdirectories with a two-digit number and
a dash, to simplify the ordering of the files.
To disable a configuration file supplied by the vendor, the
recommended way is to place a symlink to
/dev/null in the configuration directory in
/etc/, with the same filename as the vendor
All options are configured in the
Controls where to store cores. One of "
external", and "
none", the core dumps will be logged (including the backtrace if
possible), but not stored permanently. When "
default), cores will be stored in
journal", cores will be stored in the journal and rotated
following normal journal rotation patterns.
When cores are stored in the journal, they might be compressed following journal compression settings, see journald.conf(5). When cores are stored externally, they will be compressed by default, see below.
Controls compression for external
storage. Takes a boolean argument, which defaults to
The maximum size in bytes of a core which will be processed. Core dumps exceeding this size will be logged, but the backtrace will not be generated and the core will not be stored.
The maximum (uncompressed) size in bytes of a core to be saved.
Enforce limits on the disk space taken up by
externally stored core dumps.
sure that old core dumps are removed as soon as the total disk
space taken up by core dumps grows beyond this limit (defaults
to 10% of the total disk size).
controls how much disk space to keep free at least (defaults
to 15% of the total disk size). Note that the disk space used
by core dumps might temporarily exceed these limits while
core dumps are processed. Note that old core dumps are also
removed based on time via
either value to 0 to turn off size-based