teknoraver / rpms / systemd

Forked from rpms/systemd 2 months ago
Clone

Blame SOURCES/0664-man-move-description-of-Action-modes-to-FailureActio.patch

17aa40
From 12ce6830c63b4a27bb6d5b7729d70a86079b108f Mon Sep 17 00:00:00 2001
17aa40
From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= <zbyszek@in.waw.pl>
17aa40
Date: Tue, 16 Oct 2018 15:56:35 +0200
17aa40
Subject: [PATCH] man: move description of *Action= modes to
17aa40
 FailureAction=/SuccessAction=
17aa40
17aa40
FailureAction=/SuccessAction= were added later then StartLimitAction=, so it
17aa40
was easiest to refer to the existing description. But those two settings are
17aa40
somewhat simpler (they just execute the action unconditionally) while
17aa40
StartLimitAction= has additional timing and burst parameters, and they are
17aa40
about to take on a more prominent role, so let's move the description of
17aa40
allowed values.
17aa40
17aa40
(cherry picked from commit 454dd6ce7adb744584ecae9aa0bd1acf3a00e9ed)
17aa40
17aa40
Related: #1860899
17aa40
---
17aa40
 man/systemd.unit.xml | 44 +++++++++++++++++++++++---------------------
17aa40
 1 file changed, 23 insertions(+), 21 deletions(-)
17aa40
17aa40
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
17aa40
index 7605c43375..802db453a4 100644
17aa40
--- a/man/systemd.unit.xml
17aa40
+++ b/man/systemd.unit.xml
17aa40
@@ -873,6 +873,24 @@
17aa40
         </listitem>
17aa40
       </varlistentry>
17aa40
 
17aa40
+      <varlistentry>
17aa40
+        <term><varname>FailureAction=</varname></term>
17aa40
+        <term><varname>SuccessAction=</varname></term>
17aa40
+
17aa40
+        <listitem><para>Configure the action to take when the unit stops and enters a failed state or inactive
17aa40
+        state. Takes one of <option>none</option>, <option>reboot</option>, <option>reboot-force</option>,
17aa40
+        <option>reboot-immediate</option>, <option>poweroff</option>, <option>poweroff-force</option> or
17aa40
+        <option>poweroff-immediate</option>. If <option>none</option> is set, no action will be triggered.
17aa40
+        <option>reboot</option> causes a reboot following the normal shutdown procedure (i.e. equivalent to
17aa40
+        <command>systemctl reboot</command>). <option>reboot-force</option> causes a forced reboot which will
17aa40
+        terminate all processes forcibly but should cause no dirty file systems on reboot (i.e. equivalent to
17aa40
+        <command>systemctl reboot -f</command>) and <option>reboot-immediate</option> causes immediate execution of the
17aa40
+        <citerefentry><refentrytitle>reboot</refentrytitle><manvolnum>2</manvolnum></citerefentry> system call, which
17aa40
+        might result in data loss. Similarly, <option>poweroff</option>, <option>poweroff-force</option>,
17aa40
+        <option>poweroff-immediate</option> have the effect of powering down the system with similar semantics. Both
17aa40
+        options default to <option>none</option>.</para></listitem>
17aa40
+      </varlistentry>
17aa40
+
17aa40
       <varlistentry>
17aa40
         <term><varname>JobTimeoutSec=</varname></term>
17aa40
         <term><varname>JobRunningTimeoutSec=</varname></term>
17aa40
@@ -929,29 +947,13 @@
17aa40
       <varlistentry>
17aa40
         <term><varname>StartLimitAction=</varname></term>
17aa40
 
17aa40
-        <listitem><para>Configure the action to take if the rate limit configured with
17aa40
-        <varname>StartLimitIntervalSec=</varname> and <varname>StartLimitBurst=</varname> is hit. Takes one of
17aa40
-        <option>none</option>, <option>reboot</option>, <option>reboot-force</option>,
17aa40
-        <option>reboot-immediate</option>, <option>poweroff</option>, <option>poweroff-force</option> or
17aa40
-        <option>poweroff-immediate</option>. If <option>none</option> is set, hitting the rate limit will trigger no
17aa40
-        action besides that the start will not be permitted. <option>reboot</option> causes a reboot following the
17aa40
-        normal shutdown procedure (i.e. equivalent to <command>systemctl reboot</command>).
17aa40
-        <option>reboot-force</option> causes a forced reboot which will terminate all processes forcibly but should
17aa40
-        cause no dirty file systems on reboot (i.e. equivalent to <command>systemctl reboot -f</command>) and
17aa40
-        <option>reboot-immediate</option> causes immediate execution of the
17aa40
-        <citerefentry><refentrytitle>reboot</refentrytitle><manvolnum>2</manvolnum></citerefentry> system call, which
17aa40
-        might result in data loss. Similarly, <option>poweroff</option>, <option>poweroff-force</option>,
17aa40
-        <option>poweroff-immediate</option> have the effect of powering down the system with similar
17aa40
-        semantics. Defaults to <option>none</option>.</para></listitem>
17aa40
+        <listitem><para>Configure an additional action to take if the rate limit configured with
17aa40
+        <varname>StartLimitIntervalSec=</varname> and <varname>StartLimitBurst=</varname> is hit.  Takes the same
17aa40
+        values as the setting <varname>FailureAction=</varname>/<varname>SuccessAction=</varname> settings and executes
17aa40
+        the same actions. If <option>none</option> is set, hitting the rate limit will trigger no action besides that
17aa40
+        the start will not be permitted. Defaults to <option>none</option>.</para></listitem>
17aa40
       </varlistentry>
17aa40
 
17aa40
-      <varlistentry>
17aa40
-        <term><varname>FailureAction=</varname></term>
17aa40
-        <term><varname>SuccessAction=</varname></term>
17aa40
-        <listitem><para>Configure the action to take when the unit stops and enters a failed state or inactive
17aa40
-        state. Takes the same values as the setting <varname>StartLimitAction=</varname> setting and executes the same
17aa40
-        actions. Both options default to <option>none</option>.</para></listitem>
17aa40
-      </varlistentry>
17aa40
 
17aa40
       <varlistentry>
17aa40
         <term><varname>RebootArgument=</varname></term>