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 set during compilation, so configuration
25       is only needed when it is necessary to deviate from those defaults.
26       Initially, the main configuration file in /etc/systemd/ contains
27       commented out entries showing the defaults as a guide to the
28       administrator. Local overrides can be created by editing this file or
29       by creating drop-ins, as described below. Using drop-ins for local
30       configuration is recommended over modifications to the main
31       configuration file.
32
33       In addition to the "main" configuration file, drop-in configuration
34       snippets are read from /usr/lib/systemd/*.conf.d/,
35       /usr/local/lib/systemd/*.conf.d/, and /etc/systemd/*.conf.d/. Those
36       drop-ins have higher precedence and override the main configuration
37       file. Files in the *.conf.d/ configuration subdirectories are sorted by
38       their filename in lexicographic order, regardless of in which of the
39       subdirectories they reside. When multiple files specify the same
40       option, for options which accept just a single value, the entry in the
41       file sorted last takes precedence, and for options which accept a list
42       of values, entries are collected as they occur in the sorted files.
43
44       When packages need to customize the configuration, they can install
45       drop-ins under /usr/. Files in /etc/ are reserved for the local
46       administrator, who may use this logic to override the configuration
47       files installed by vendor packages. Drop-ins have to be used to
48       override package drop-ins, since the main configuration file has lower
49       precedence. It is recommended to prefix all filenames in those
50       subdirectories with a two-digit number and a dash, to simplify the
51       ordering of the files.
52
53       To disable a configuration file supplied by the vendor, the recommended
54       way is to place a symlink to /dev/null in the configuration directory
55       in /etc/, with the same filename as the vendor configuration file.
56

OPTIONS

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

SEE ALSO

109       systemd-journald.service(8), coredumpctl(1), systemd-tmpfiles(8)
110
111
112
113systemd 250                                                   COREDUMP.CONF(5)
Impressum