man: Clarify when OnFailure= activates after restarts (#7646)

This commit is contained in:
Ken (Bitsko) MacLeod 2017-12-15 04:10:41 -06:00 committed by Zbigniew Jędrzejewski-Szmek
parent f1d34068ef
commit bd2538b50b
3 changed files with 11 additions and 7 deletions

View File

@ -754,7 +754,8 @@
limiting configured with <varname>StartLimitIntervalSec=</varname>
and <varname>StartLimitBurst=</varname>, see
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details.</para>
for details. A restarted service enters the failed state only
after the start limits are reached.</para>
<para>Setting this to <option>on-failure</option> is the
recommended choice for long-running services, in order to

View File

@ -665,7 +665,9 @@
<listitem><para>A space-separated list of one or more units
that are activated when this unit enters the
<literal>failed</literal> state.</para></listitem>
<literal>failed</literal> state. A service unit using
<varname>Restart=</varname> enters the failed state only after
the start limits are reached.</para></listitem>
</varlistentry>
<varlistentry>

View File

@ -297,11 +297,12 @@
states are called "activating", "deactivating"). A special
"failed" state is available as well, which is very similar to
"inactive" and is entered when the service failed in some way
(process returned error code on exit, or crashed, or an operation
timed out). If this state is entered, the cause will be logged,
for later reference. Note that the various unit types may have a
number of additional substates, which are mapped to the five
generalized unit states described here.</para>
(process returned error code on exit, or crashed, an operation
timed out, or after too many restarts). If this state is entered,
the cause will be logged, for later reference. Note that the
various unit types may have a number of additional substates,
which are mapped to the five generalized unit states described
here.</para>
<para>The following unit types are available:</para>