From: Dave Reisner <dreisner@archlinux.org>
Date: Fri, 14 Feb 2014 00:40:04 +0000 (+0100)
Subject: man: systemd.service(5): clarify behavior of SuccessExitStatus
X-Git-Tag: v209~142
X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=29e254f7f093c07a1ec7e845e60203357f585235;hp=112cfb181453e38d3ef4a74fba23abbb53392002

man: systemd.service(5): clarify behavior of SuccessExitStatus

The behavior of this is a little cryptic in that $MAINPID must exit as
a direct result of receiving a signal in order for a listed signal to
be considered a success condition.
---

diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index d316ab5d2..72b872bec 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -748,7 +748,10 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}
                                 <constant>SIGTERM</constant>, and <constant>SIGPIPE</constant>. Exit status
                                 definitions can either be numeric exit
                                 codes or termination signal names,
-                                separated by spaces. For example:
+                                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:
 				<programlisting>SuccessExitStatus=1 2 8 <constant>SIGKILL</constant></programlisting>
 				ensures that exit codes 1, 2, 8 and
 				the termination signal