diff options
| author | Mathieu Bridon <bochecha@fedoraproject.org> | 2013-03-13 12:43:40 +0800 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2013-03-13 00:51:35 -0400 |
| commit | 3ae390ba020fd6c8bad9a6b384a6ff56c9fe5f5b (patch) | |
| tree | 62ccac78902e4f044f301b5cbc2c5eec5ebf4819 /man | |
| parent | 702f64b93cb215d43f673dd4b2f3646b879c566e (diff) | |
| download | systemd-3ae390ba020fd6c8bad9a6b384a6ff56c9fe5f5b.tar.gz | |
man: Document the actual behaviour of ExecStopPost
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.
Diffstat (limited to 'man')
| -rw-r--r-- | man/systemd.service.xml | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 8977873c1e..b8b19b386a 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -464,9 +464,12 @@ <term><varname>ExecStopPost=</varname></term> <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 |