X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.service.xml;h=5b3afb86d2c64d65830bc75c61c6e68fca25ad89;hb=2292547af9638e2b3f7e0e96a56dd6c909e516dc;hp=8ad665643db0202b6bdaa2dc248cb2a34afc8ccb;hpb=b200a92cdc47b204e2ed7fbdd1eaf15abfd019c6;p=elogind.git
diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index 8ad665643..5b3afb86d 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -674,7 +674,7 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}
processes specified with
ExecStartPre=,
ExecStartPost=,
- ExecStopPre=,
+ ExecStop=,
ExecStopPost=, or
ExecReload=.
When the death of the process is a
@@ -747,10 +747,7 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}
SIGTERM, and SIGPIPE. Exit status
definitions can either be numeric exit
codes or termination signal names,
- separated by spaces. Signals will only
- be considered if the service does not implement
- a signal handler and exits as a direct result
- of receiving the signal. For example:
+ separated by spaces. For example:
SuccessExitStatus=1 2 8 SIGKILL
ensures that exit codes 1, 2, 8 and
the termination signal
@@ -767,7 +764,7 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}
Programs should instead perform cleanup and kill themselves with the same signal instead. See
Proper handling of SIGINT/SIGQUIT â How to be a proper program.
- This option may appear more than once
+ This option may appear more than once,
in which case the list of successful
exit statuses is merged. If the empty
string is assigned to this option, the