diff options
| author | Dave Reisner <dreisner@archlinux.org> | 2014-02-14 01:40:04 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2014-02-14 01:40:52 +0100 |
| commit | 29e254f7f093c07a1ec7e845e60203357f585235 (patch) | |
| tree | 04cdd042b2a32759a00198c7ae594f2848c6c354 | |
| parent | 112cfb181453e38d3ef4a74fba23abbb53392002 (diff) | |
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.
| -rw-r--r-- | man/systemd.service.xml | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index d316ab5d2e..72b872bece 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 |