shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-25 01:34:28 +03:00
Code

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

Browse Source 
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.
This commit is contained in:
Dave Reisner 2014-02-14 01:40:04 +01:00 committed by Lennart Poettering
parent 112cfb1814
commit 29e254f7f0
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
man/systemd.service.xml
View File

@ -748,7 +748,10 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}
<constant>SIGTERM</constant>, and <constant>SIGPIPE</constant>. Exit status <constant>SIGTERM</constant>, and <constant>SIGPIPE</constant>. Exit status
definitions can either be numeric exit definitions can either be numeric exit
codes or termination signal names, 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> <programlisting>SuccessExitStatus=1 2 8 <constant>SIGKILL</constant></programlisting>
ensures that exit codes 1, 2, 8 and ensures that exit codes 1, 2, 8 and
the termination signal the termination signal