From: David Tardon Date: Fri, 19 Mar 2021 09:05:47 +0000 (+0100) Subject: man: document differences in clean exit status for Type=oneshot X-Git-Tag: v248-2~33 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f055cf77862bc580f3afbfaac161d1c060f39411;p=thirdparty%2Fsystemd.git man: document differences in clean exit status for Type=oneshot See commit 1f0958f640b87175cd547c1e69084cfe54a22e9d . --- diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 501da54b8aa..350bc5f8e5b 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -756,14 +756,19 @@ If set to (the default), the service will not be restarted. If set to , it will be restarted only when the service process exits cleanly. - In this context, a clean exit means an exit code of 0, or one - of the signals - SIGHUP, - SIGINT, - SIGTERM or - SIGPIPE, and - additionally, exit statuses and signals specified in - SuccessExitStatus=. If set to + In this context, a clean exit means any of the following: + + exit code of 0; + for types other than + Type=oneshot, one of the signals + SIGHUP, + SIGINT, + SIGTERM, or + SIGPIPE; + exit statuses and signals specified in + SuccessExitStatus=. + + If set to , the service will be restarted when the process exits with a non-zero exit code, is terminated by a signal (including on core dump, but excluding @@ -885,7 +890,7 @@ Takes a list of exit status definitions that, when returned by the main service process, will be considered successful termination, in addition to the normal successful exit status - 0 and the signals SIGHUP, SIGINT, + 0 and, except for Type=oneshot, the signals SIGHUP, SIGINT, SIGTERM, and SIGPIPE. Exit status definitions can be numeric termination statuses, termination status names, or termination signal names, separated by spaces. See the Process Exit Codes section in