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.

(cherry picked from commit 5501da15ba34284e50c10ccd6b3ffa8838bb431b)
(cherry picked from commit fb2afc5f30c76965c3a2b5a0f3cc6170b59a6fa4)

diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index 040b8e28939eadd20bbc887823f67c21e0c008e7..f710f6a940637f8fcc9c567f0d269fd9b41cdea9 100644 (file)
--- a/man/systemd.timer.xml
+++ b/man/systemd.timer.xml
@@ -297,9 +297,10 @@
 
         <listitem><para>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 <varname>OnCalendar=</varname>. 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 <varname>RandomizedDelaySec=</varname>.
+        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 <varname>OnCalendar=</varname>. Defaults to
         <varname>false</varname>.</para>
 
         <para>Use <command>systemctl clean --what=state …</command> on the timer unit to remove the timestamp