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/. Files in /etc/ are reserved for the
33       local administrator, who may use this logic to override the
34       configuration files installed by vendor packages. The main
35       configuration file is read before any of the configuration directories,
36       and has the lowest precedence; entries in a file in any configuration
37       directory override entries in the single configuration file. Files in
38       the *.conf.d/ configuration subdirectories are sorted by their filename
39       in lexicographic order, regardless of which of the subdirectories they
40       reside in. When multiple files specify the same option, for options
41       which accept just a single value, the entry in the file with the
42       lexicographically latest name takes precedence. For options which
43       accept a list of values, entries are collected as they occur in files
44       sorted lexicographically. It is recommended to prefix all filenames in
45       those subdirectories with a two-digit number and a dash, to simplify
46       the ordering of the files.
47
48       To disable a configuration file supplied by the vendor, the recommended
49       way is to place a symlink to /dev/null in the configuration directory
50       in /etc/, with the same filename as the vendor configuration file.
51

OPTIONS

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

SEE ALSO

99       systemd-journald.service(8), coredumpctl(1), systemd-tmpfiles(8)
100
101
102
103systemd 243                                                   COREDUMP.CONF(5)
Impressum