[systemd-devel] [PATCH] systemd.service(5): clarify behavior of SuccessExitStatus

[Lennart Poettering]

On Fri, 27.12.13 10:46, Dave Reisner (dreisner at archlinux.org) wrote:

> 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.

Applied! Thanks!

> ---
>  man/systemd.service.xml | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/man/systemd.service.xml b/man/systemd.service.xml
> index 27f069f..c3a9307 100644
> --- a/man/systemd.service.xml
> +++ b/man/systemd.service.xml
> @@ -737,7 +737,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. 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. Example:
>                                  <literal>SuccessExitStatus=1 2 8
>                                  <constant>SIGKILL</constant></literal>, ensures that exit
>                                  codes 1, 2, 8 and the termination


Lennart

-- 
Lennart Poettering, Red Hat