chiark / gitweb /
man: systemd.service(5): clarify behavior of SuccessExitStatus
authorDave Reisner <dreisner@archlinux.org>
Fri, 14 Feb 2014 00:40:04 +0000 (01:40 +0100)
committerLennart Poettering <lennart@poettering.net>
Fri, 14 Feb 2014 00:40:52 +0000 (01:40 +0100)
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.

man/systemd.service.xml

index d316ab5..72b872b 100644 (file)
@@ -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