coredump (5) - Linux Man Pages
coredump: Coredump storage configuration file
coredump.conf - Coredump storage configuration file
All options are configured in the "[Coredump]" section:
Controls where to store cores. One of
"none", the coredumps will be logged but not stored permanently. When
(the default), cores will be stored in
"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.
- Controls the type of compression for external storage. Takes a boolean argument, defaults to "yes".
- 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.
- The maximum (uncompressed) size in bytes of a core to be saved.
- 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).