man: extend documentation for RestartPreventExitStatus= and SuccessExitStatus= a bit
This commit is contained in:
parent
96342de68d
commit
abdf799316
1
TODO
1
TODO
|
@ -397,6 +397,7 @@ Features:
|
||||||
- resource control in systemd
|
- resource control in systemd
|
||||||
- inhibiting
|
- inhibiting
|
||||||
- testing with Harald's awesome test kit
|
- testing with Harald's awesome test kit
|
||||||
|
- restart
|
||||||
|
|
||||||
* allow port=0 in .socket units
|
* allow port=0 in .socket units
|
||||||
|
|
||||||
|
|
|
@ -580,17 +580,46 @@
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>RestartPreventExitStatus=</varname></term>
|
<term><varname>SuccessExitStatus=</varname></term>
|
||||||
<listitem><para>Specify exit status list, which
|
<listitem><para>Takes a list of exit
|
||||||
will prevent service from restart. Codes are
|
status definitions that when returned
|
||||||
separated by whitespace (e.g. "1 6 SIGKILL").</para></listitem>
|
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>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>SuccessExitStatus=</varname></term>
|
<term><varname>RestartPreventExitStatus=</varname></term>
|
||||||
<listitem><para>Specify exit status list, which
|
<listitem><para>Takes a list of exit
|
||||||
will be considered as successful exit. Codes are
|
status definitions that when returned
|
||||||
separated by whitespace (e.g. "1 6 SIGKILL").</para></listitem>
|
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>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
|
Loading…
Reference in New Issue