summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2012-08-14 18:37:45 +0200
committerLennart Poettering <lennart@poettering.net>2012-08-14 18:37:45 +0200
commitabdf7993161a2762df6887fdb5a5f0f4f5da24cf (patch)
tree9a21a600bf1c3516e054c115b9f696a8563b9776 /man
parent96342de68d0d6de71a062d984dafd2a0905ed9fe (diff)
man: extend documentation for RestartPreventExitStatus= and SuccessExitStatus= a bit
Diffstat (limited to 'man')
-rw-r--r--man/systemd.service.xml45
1 files changed, 37 insertions, 8 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index c4bd65e349..72b67c6988 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -580,17 +580,46 @@
</varlistentry>
<varlistentry>
- <term><varname>RestartPreventExitStatus=</varname></term>
- <listitem><para>Specify exit status list, which
- will prevent service from restart. Codes are
- separated by whitespace (e.g. "1 6 SIGKILL").</para></listitem>
+ <term><varname>SuccessExitStatus=</varname></term>
+ <listitem><para>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
+ code 0 and the signals SIGHUP, SIGINT,
+ SIGTERM and SIGPIPE. Exit status
+ definitions can either be numeric exit
+ codes or termination signal names, and
+ are are separated by spaces. Example:
+ "<literal>SuccessExitStatus=1 2 8
+ SIGKILL</literal>", ensures that exit
+ codes 1, 2, 8 and the termination
+ signal SIGKILL are considered clean
+ service
+ terminations.</para></listitem>
</varlistentry>
<varlistentry>
- <term><varname>SuccessExitStatus=</varname></term>
- <listitem><para>Specify exit status list, which
- will be considered as successful exit. Codes are
- separated by whitespace (e.g. "1 6 SIGKILL").</para></listitem>
+ <term><varname>RestartPreventExitStatus=</varname></term>
+ <listitem><para>Takes a list of exit
+ status definitions that when returned
+ by the main service process will
+ prevent automatic service restarts
+ regardless of the restart setting
+ configured with
+ <varname>Restart=</varname>. Exit
+ status definitions can either be
+ numeric exit codes or termination
+ signal names, and are separated by
+ spaces. Defaults to the empty list, so
+ that by default no exit status is
+ excluded from the configured restart
+ logic. Example:
+ "<literal>RestartPreventExitStatus=1 6
+ SIGABRT</literal>", ensures that exit
+ codes 1 and 6 and the termination signal
+ SIGABRT will not result in automatic
+ service restarting.</para></listitem>
</varlistentry>
<varlistentry>