1COREDUMP.CONF(5) coredump.conf COREDUMP.CONF(5)
2
6 coredump.conf, coredump.conf.d - Coredump storage configuration files
7
9 /etc/systemd/coredump.conf
10 /etc/systemd/coredump.conf.d/*.conf
12 /run/systemd/coredump.conf.d/*.conf
14 /usr/lib/systemd/coredump.conf.d/*.conf
16
18 These files configure the behaviour of systemd-coredump(8), a handler
19 for core dumps invoked by the kernel.
20
22 Default configuration is defined during compilation, so a configuration
23 file is only needed when it is necessary to deviate from those
24 defaults. By default the configuration file in /etc/systemd/ contains
25 commented out entries showing the defaults as a guide to the
26 administrator. This file can be edited to create local overrides.
27 When packages need to customize the configuration, they can install
29 configuration snippets in /usr/lib/systemd/*.conf.d/. Files in /etc/
30 are reserved for the local administrator, who may use this logic to
31 override the configuration files installed by vendor packages. The main
32 configuration file is read before any of the configuration directories,
33 and has the lowest precedence; entries in a file in any configuration
34 directory override entries in the single configuration file. Files in
35 the *.conf.d/ configuration subdirectories are sorted by their filename
36 in lexicographic order, regardless of which of the subdirectories they
37 reside in. If multiple files specify the same option, the entry in the
38 file with the lexicographically latest name takes precedence. It is
39 recommended to prefix all filenames in those subdirectories with a
40 two-digit number and a dash, to simplify the ordering of the files.
41 To disable a configuration file supplied by the vendor, the recommended
43 way is to place a symlink to /dev/null in the configuration directory
44 in /etc/, with the same filename as the vendor configuration file.
45
47 All options are configured in the "[Coredump]" section:
48 Storage=
50 Controls where to store cores. One of "none", "external",
51 "journal", and "both". When "none", the coredumps will be logged
52 but not stored permanently. When "external" (the default), cores
53 will be stored in /var/lib/systemd/coredump. When "journal", cores
54 will be stored in the journal and rotated following normal journal
55 rotation patterns. When "both", cores will be stored in both
56 locations.
57 When cores are stored in the journal, they might be compressed
59 following journal compression settings, see journald.conf(5). When
60 cores are stored externally, they will be compressed by default,
61 see below.
62 Compress=
64 Controls compression for external storage. Takes a boolean
65 argument, defaults to "yes".
66 ProcessSizeMax=
68 The maximum size in bytes of a core which will be processed.
69 Coredumps exceeding this size will be logged, but the backtrace
70 will not be generated and the core will not be stored.
71 ExternalSizeMax=, JournalSizeMax=
73 The maximum (uncompressed) size in bytes of a core to be saved.
74 MaxUse=, KeepFree=
76 Enforce limits on the disk space taken up by externally stored
77 coredumps. MaxUse= makes sure that old coredumps are removed as
78 soon as the total disk space taken up by coredumps grows beyond
79 this limit (defaults to 10% of the total disk size). KeepFree=
80 controls how much disk space to keep free at least (defaults to 15%
81 of the total disk size). Note that the disk space used by coredumps
82 might temporarily exceed these limits while coredumps are
83 processed. Note that old coredumps are also removed based on time
84 via systemd-tmpfiles(8). Set either value to 0 to turn off size
85 based clean-up.
86
88 systemd-journald.service(8), coredumpctl(1), systemd-tmpfiles(8)
89systemd 219 COREDUMP.CONF(5)