[systemd-devel] [PATCH] man: Document the actual behaviour of ExecStopPost

Mathieu Bridon bochecha at fedoraproject.org
Tue Mar 12 21:43:40 PDT 2013

The documentation makes it sound like ExecStopPost is only run when
stopping the service with `systemctl stop foo.service`

However, that is not the case, as it also gets run when the service
unexpectedly exists, crashes, or gets SIGKILLed.
 man/systemd.service.xml | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index 8977873..b8b19b3 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -464,9 +464,12 @@
                                 <listitem><para>Additional commands
                                 that are executed after the service
-                                was stopped using the commands
-                                configured in
-                                <varname>ExecStop=</varname>. This
+                                was stopped. This includes cases where
+                                the commands configured in
+                                <varname>ExecStop=</varname> were used,
+                                where the service doesn't have any
+                                <varname>ExecStop=</varname> defined, or
+                                where the service exited unexpectedly. This
                                 argument takes multiple command lines,
                                 following the same scheme as described
                                 for <varname>ExecStart</varname>. Use

More information about the systemd-devel mailing list