X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.timer.xml;h=55b458557f357634ae7f27591cbd8cddf7001e30;hb=37161c5148396448921841ae1026b281c7949652;hp=484287ccf67fc3f770f6883e8f7df6039e8b4d3e;hpb=9f5eb56a13dee1085cbf2560ac3afd73f72402cb;p=elogind.git
diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index 484287ccf..55b458557 100644
--- a/man/systemd.timer.xml
+++ b/man/systemd.timer.xml
@@ -78,15 +78,20 @@
Unit= (see below).
Unless DefaultDependencies=
- is set to , timer units will
+ is set to , all timer units will
implicitly have dependencies of type
Conflicts= and
Before= on
- shutdown.target. These ensure
- that timer units are stopped cleanly prior to system
- shutdown. Only timer units involved with early boot or
- late system shutdown should disable this
- option.
+ shutdown.target to ensure that
+ they are stopped cleanly prior to system shutdown.
+ Timer units with at least one
+ OnCalendar= directive will have an
+ additional After= dependency on
+ timer-sync.target to avoid
+ being started before the system clock has been
+ correctly set. Only timer units involved with early
+ boot or late system shutdown should disable the
+ DefaultDependencies= option.
@@ -141,7 +146,7 @@
also include time units. Example:
"OnBootSec=5h 30min" means 5 hours and
30 minutes after boot-up. For details
- about the syntax of time spans see
+ about the syntax of time spans, see
systemd.unit5.
If a timer configured with
@@ -165,8 +170,8 @@
assignments will have no
effect.
- Note that timers are not
- necessarily expired at the precise
+ Note that timers do not
+ necessarily expire at the precise
time configured with these settings,
as they are subject to the
AccuracySec=
@@ -182,13 +187,13 @@
event expressions. See
systemd.time7
for more information on the syntax of
- calendar event expressions. Otherwise
+ calendar event expressions. Otherwise,
the semantics are similar to
OnActiveSec= and
related settings.
- Note that timers are not
- necessarily expired at the precise
+ Note that timers do not
+ necessarily expire at the precise
time configured with this setting,
as it is subject to the
AccuracySec=
@@ -201,7 +206,7 @@
Specify the accuracy
the timer shall elapse with. Defaults
to 1min. The timer is scheduled to
- expire within a time window starting
+ elapse within a time window starting
with the time specified in
OnCalendar=,
OnActiveSec=,
@@ -211,16 +216,16 @@
OnUnitInactiveSec=
and ending the time configured with
AccuracySec=
- later. Within this time window the
+ later. Within this time window, the
expiry time will be placed at a
host-specific, randomized but stable
- position, that is synchronized between
+ position that is synchronized between
all local timer units. This is done in
order to distribute the wake-up time
in networked installations, as well as
optimizing power consumption to
suppress unnecessary CPU wake-ups. To
- get best accuracy set this option to
+ get best accuracy, set this option to
1us. Note that the timer is still
subject to the timer slack configured
via
@@ -229,7 +234,7 @@
setting. See
prctl2
for details. To optimize power
- consumption make sure to set this
+ consumption, make sure to set this
value as high as possible and as low
as necessary.
@@ -249,6 +254,43 @@
are named identically, except for the
suffix.
+
+
+
+ Persistent=
+
+ 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 machine
+ was off. Note that this setting only
+ has an effect on timers configured
+ with OnCalendar=.
+
+
+
+
+ WakeSystem=
+
+ Takes a boolean
+ argument. If true, an elapsing timer
+ will cause the system to resume from
+ suspend, should it be suspended and if
+ the system supports this. Note that
+ this option will only make sure the
+ system resumes on the appropriate
+ times, it will not take care of
+ suspending it again after any work
+ that is to be done is
+ finished. Defaults to
+ false.
+
@@ -256,7 +298,7 @@
See Alsosystemd1,
- systemctl8,
+ systemctl1,
systemd.unit5,
systemd.service5,
systemd.time7,