From 6dfde7acf1405adbb7adb2adc6969c4eb3c0990a Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Tue, 5 Apr 2016 21:00:10 -0400 Subject: man: also mention systemd-coredump@.service and systemd-coredump.socket Added in 3c171f0b1e. --- man/systemd-coredump.xml | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'man/systemd-coredump.xml') diff --git a/man/systemd-coredump.xml b/man/systemd-coredump.xml index aa352448b2..51dc27e8d3 100644 --- a/man/systemd-coredump.xml +++ b/man/systemd-coredump.xml @@ -45,11 +45,15 @@ systemd-coredump + systemd-coredump.socket + systemd-coredump@.service Log and store core dumps /usr/lib/systemd/systemd-coredump + systemd-coredump@.service + systemd-coredump.socket @@ -85,6 +89,13 @@ backtrace if possible, and store the core (contents of process' memory contents) in an external file on disk in /var/lib/systemd/coredump. + When the kernel invokes systemd-coredump to handle a coredump, + it will connect to the socket created by the systemd-coredump.socket + unit, which in turn will spawn a systemd-coredump@.service instance + to process the coredump. Hence systemd-coredump.socket + and systemd-coredump@.service are helper units which do the actual + processing of coredumps and are subject to normal service management. + The log entry and a backtrace are stored in the journal, and can be viewed with journalctl1. coredumpctl1 -- cgit v1.2.3-54-g00ecf