huschi.net

COREDUMP.CONF(5)                 coredump.conf                COREDUMP.CONF(5)

NAME
       coredump.conf, coredump.conf.d - Coredump storage configuration files
SYNOPSIS
       /etc/systemd/coredump.conf
       /etc/systemd/coredump.conf.d/*.conf
       /run/systemd/coredump.conf.d/*.conf
       /usr/lib/systemd/coredump.conf.d/*.conf
DESCRIPTION
       These files configure the behaviour of systemd-coredump(8), a handler
       for core dumps invoked by the kernel.
CONFIGURATION DIRECTORIES AND PRECEDENCE
       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 *.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.
OPTIONS
       All 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.conf(5). When
           cores are stored externally, they will be compressed by default,
           see below.
       Compress=
           Controls 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.  MaxUse= 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).  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 coredumps
           might temporarily exceed these limits while coredumps are
           processed. Note that old coredumps are also removed based on time
           via systemd-tmpfiles(8). Set either value to 0 to turn off size
           based clean-up.
SEE ALSO
       systemd-journald.service(8), coredumpctl(1), systemd-tmpfiles(8)

systemd 219                                                   COREDUMP.CONF(5)