systemd-coredump man page
systemd-coredump — Log and store core dumps
systemd-coredump can be used as a helper binary by the kernel when a user space program receives a fatal signal and dumps core. For it to be used in this capacity, it must be specified by the kernel.core_pattern sysctl(8) setting. Systemd installs
/usr/lib/sysctl.d/50-coredump.conf which configures kernel.core_pattern to invoke
systemd-coredump. This file may be masked or overridden to use a different setting following normal sysctl.d(5) rules.
The behaviour of a specific program upon reception of a signal is governed by a few factors which are described in detail in core(5). In particular, the coredump will only be processed when the related resource limits are high enough. For programs started by
systemd those may be set using LimitCore= (see systemd.exec(5)).
systemd-coredump will log the coredump including a backtrace if possible, and store the core (contents of process' memory contents) in an external file on disk in
/var/lib/systemd/coredump, or directly in the journal. This behaviour may be modified using coredump.conf(5).
Apart from the journalctl(1) log viewer, coredumpctl(1) may be used to list and extract coredumps.
coredump.conf(5), coredumpctl(1), systemd-journald.service(8), core(5), sysctl.d(5), systemd-sysctl.service(8).
coredump.conf(5), coredumpctl(1), systemd.directives(7), systemd.index(7), systemd-journald.service(8).
Explore man page connections for systemd-coredump(8).
systemd-coredump@.service(8) and systemd-coredump.socket(8) are aliases of systemd-coredump(8).