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
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 *.conf.d/ configuration subdirectories are sorted
by their filename in lexicographic order, regardless of which of the
subdirectories they reside in. If multiple files specify the same
option, the entry in the file with the lexicographically latest name
takes precedence. 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 configuration file.
All options are configured in the "[Coredump]" section:
Controls where to store cores. One of "none", "external", and
"journal". When "none", the core dumps will be logged (including
the backtrace if possible), but not stored permanently. When
"external" (the default), cores will be stored in
/var/lib/systemd/coredump/. When "journal", cores will be stored
in the journal and rotated following normal journal rotation
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 "yes".
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. MaxUse= makes 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).
KeepFree= 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 systemd-tmpfiles(8). Set either value
to 0 to turn off size-based clean-up.
This page is part of the systemd (systemd system and service manager)
project. Information about the project can be found at
⟨http://www.freedesktop.org/wiki/Software/systemd⟩. If you have a bug
report for this manual page, see
page was obtained from the project's upstream Git repository
⟨https://github.com/systemd/systemd.git⟩ on 2017-03-13. If you dis‐
cover any rendering problems in this HTML version of the page, or you
believe there is a better or more up-to-date source for the page, or
you have corrections or improvements to the information in this
COLOPHON (which is not part of the original manual page), send a mail
systemd 233 COREDUMP.CONF(5)