picnoir/Systemd
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

man: Document the actual behaviour of ExecStopPost

Browse source 
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.
This commit is contained in:
Mathieu Bridon 2013-03-13 12:43:40 +08:00 committed by Zbigniew Jędrzejewski-Szmek
parent 702f64b93c
commit 3ae390ba02
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
man/systemd.service.xml
View file

@ -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