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

[elogind.git] / man / systemd.service.xml

diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index d316ab5d2ef3e465a99425e7dc6f30fba93260cf..72b872beced11be7146da478c10c6dd3913b548e 100644 (file)
--- 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,
                                 <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
                                <programlisting>SuccessExitStatus=1 2 8 <constant>SIGKILL</constant></programlisting>
                                ensures that exit codes 1, 2, 8 and
                                the termination signal