From 5501da15ba34284e50c10ccd6b3ffa8838bb431b Mon Sep 17 00:00:00 2001 From: Nazar Vinnichuk Date: Fri, 11 Sep 2020 13:38:53 +0300 Subject: [PATCH] man: document the random delay of persistent timers The manual states that a persistent timer triggers it's service immediately on activation to catch up with missed invocations, but since PR #11608 it is no longer the case if RandomizedDelaySec= is set to a non-zero value. --- man/systemd.timer.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml index 5822402712..32ddb1c6e4 100644 --- a/man/systemd.timer.xml +++ b/man/systemd.timer.xml @@ -297,9 +297,10 @@ Takes a boolean argument. If true, the time when the service unit was last triggered is stored on disk. When the timer is activated, the service unit is triggered immediately if it - would have been triggered at least once during the time when the timer was inactive. This is useful - to catch up on missed runs of the service when the system was powered down. Note that this setting - only has an effect on timers configured with OnCalendar=. Defaults to + would have been triggered at least once during the time when the timer was inactive. Such triggering + is nonetheless subject to the delay imposed by RandomizedDelaySec=. + This is useful to catch up on missed runs of the service when the system was powered down. Note that + this setting only has an effect on timers configured with OnCalendar=. Defaults to false. Use systemctl clean --what=state … on the timer unit to remove the timestamp