1COREDUMP.CONF(5)                 coredump.conf                COREDUMP.CONF(5)
2
3
4

NAME

6       coredump.conf, coredump.conf.d - Core dump storage configuration files
7

SYNOPSIS

9       /etc/systemd/coredump.conf
10
11       /etc/systemd/coredump.conf.d/*.conf
12
13       /run/systemd/coredump.conf.d/*.conf
14
15       /usr/lib/systemd/coredump.conf.d/*.conf
16

DESCRIPTION

18       These files configure the behavior of systemd-coredump(8), a handler
19       for core dumps invoked by the kernel. Whether systemd-coredump is used
20       is determined by the kernel's kernel.core_pattern sysctl(8) setting.
21       See systemd-coredump(8) and core(5) pages for the details.
22

CONFIGURATION DIRECTORIES AND PRECEDENCE

24       The default configuration is defined during compilation, so a
25       configuration file is only needed when it is necessary to deviate from
26       those defaults. By default, the configuration file in /etc/systemd/
27       contains commented out entries showing the defaults as a guide to the
28       administrator. This file can be edited to create local overrides.
29
30       When packages need to customize the configuration, they can install
31       configuration snippets in /usr/lib/systemd/*.conf.d/ or
32       /usr/local/lib/systemd/*.conf.d/. The main configuration file is read
33       before any of the configuration directories, and has the lowest
34       precedence; entries in a file in any configuration directory override
35       entries in the single configuration file. Files in the *.conf.d/
36       configuration subdirectories are sorted by their filename in
37       lexicographic order, regardless of in which of the subdirectories they
38       reside. When multiple files specify the same option, for options which
39       accept just a single value, the entry in the file with the
40       lexicographically latest name takes precedence. For options which
41       accept a list of values, entries are collected as they occur in files
42       sorted lexicographically.
43
44       Files in /etc/ are reserved for the local administrator, who may use
45       this logic to override the configuration files installed by vendor
46       packages. It is recommended to prefix all filenames in those
47       subdirectories with a two-digit number and a dash, to simplify the
48       ordering of the files.
49
50       To disable a configuration file supplied by the vendor, the recommended
51       way is to place a symlink to /dev/null in the configuration directory
52       in /etc/, with the same filename as the vendor configuration file.
53

OPTIONS

55       All options are configured in the "[Coredump]" section:
56
57       Storage=
58           Controls where to store cores. One of "none", "external", and
59           "journal". When "none", the core dumps may be logged (including the
60           backtrace if possible), but not stored permanently. When "external"
61           (the default), cores will be stored in /var/lib/systemd/coredump/.
62           When "journal", cores will be stored in the journal and rotated
63           following normal journal rotation patterns.
64
65           When cores are stored in the journal, they might be compressed
66           following journal compression settings, see journald.conf(5). When
67           cores are stored externally, they will be compressed by default,
68           see below.
69
70       Compress=
71           Controls compression for external storage. Takes a boolean
72           argument, which defaults to "yes".
73
74       ProcessSizeMax=
75           The maximum size in bytes of a core which will be processed. Core
76           dumps exceeding this size may be stored, but the backtrace will not
77           be generated.
78
79           Setting Storage=none and ProcessSizeMax=0 disables all coredump
80           handling except for a log entry.
81
82       ExternalSizeMax=, JournalSizeMax=
83           The maximum (uncompressed) size in bytes of a core to be saved.
84
85       MaxUse=, KeepFree=
86           Enforce limits on the disk space taken up by externally stored core
87           dumps.  MaxUse= makes sure that old core dumps are removed as soon
88           as the total disk space taken up by core dumps grows beyond this
89           limit (defaults to 10% of the total disk size).  KeepFree= controls
90           how much disk space to keep free at least (defaults to 15% of the
91           total disk size). Note that the disk space used by core dumps might
92           temporarily exceed these limits while core dumps are processed.
93           Note that old core dumps are also removed based on time via
94           systemd-tmpfiles(8). Set either value to 0 to turn off size-based
95           clean-up.
96
97       The defaults for all values are listed as comments in the template
98       /etc/systemd/coredump.conf file that is installed by default.
99

SEE ALSO

101       systemd-journald.service(8), coredumpctl(1), systemd-tmpfiles(8)
102
103
104
105systemd 245                                                   COREDUMP.CONF(5)
Impressum