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