coredump.confsystemdDeveloperLennartPoetteringlennart@poettering.netcoredump.conf5coredump.confcoredump.conf.dCoredump storage configuration files/etc/systemd/coredump.conf/etc/systemd/coredump.conf.d/*.conf/run/systemd/coredump.conf.d/*.conf/usr/lib/systemd/coredump.conf.d/*.confDescriptionThese files configure the behaviour of systemd-coredump,
a handler for core dumps invoked by the kernel.OptionsAll options are configured in the
[Coredump] section:Storage=Controls where to store cores. One of
none, external,
journal, and both. When
none, the coredumps will be logged 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 patterns. When both, cores
will be stored in both locations.When cores are stored in the journal, they might be
compressed following journal compression settings, see
journald.conf5.
When cores are stored externally, they will be compressed
by default, see below.Compress=Controls the type of compression for external
storage. Takes a boolean argument, defaults to
yes.ProcessSizeMax=The maximum size in bytes of a core
which will be processed. Coredumps exceeding this size
will be logged, but the backtrace will not be generated
and the core will not be stored.ExternalSizeMax=JournalSizeMax=The maximum (uncompressed) size in bytes of a
core to be saved.MaxUse=KeepFree=Enforce limits on the disk space taken up by
externally stored coredumps. makes
sure that old coredumps are removed as soon as the total disk
space taken up by coredumps 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 coredumps might temporarily exceed these limits while
coredumps are processed. Note that old coredumps are also
removed based on time via
systemd-tmpfiles8.See Alsosystemd-journald.service8,
coredumpctl1,
systemd-tmpfiles8