diff --git a/Makefile-man.am b/Makefile-man.am
index a7e348b1f13..db9b0904322 100644
--- a/Makefile-man.am
+++ b/Makefile-man.am
@@ -1849,11 +1849,21 @@ MANPAGES += \
man/coredumpctl.1 \
man/systemd-coredump.8
MANPAGES_ALIAS += \
- man/coredump.conf.d.5
+ man/coredump.conf.d.5 \
+ man/systemd-coredump.socket.8 \
+ man/systemd-coredump@.service.8
man/coredump.conf.d.5: man/coredump.conf.5
+man/systemd-coredump.socket.8: man/systemd-coredump.8
+man/systemd-coredump@.service.8: man/systemd-coredump.8
man/coredump.conf.d.html: man/coredump.conf.html
$(html-alias)
+man/systemd-coredump.socket.html: man/systemd-coredump.html
+ $(html-alias)
+
+man/systemd-coredump@.service.html: man/systemd-coredump.html
+ $(html-alias)
+
endif
if ENABLE_EFI
diff --git a/man/systemd-coredump.xml b/man/systemd-coredump.xml
index aa352448b20..51dc27e8d36 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