X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.timer.xml;h=58eaab09f84625cbb20d109067a5b5aa625bcb5b;hp=659bc81ccd9d69f2245c6d017b48a6a0687a5d1a;hb=0088d63151e088d62104d88f866e9eb049091c22;hpb=79640424059328268b9fb6c5fa8eb777b27a177e
diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index 659bc81cc..58eaab09f 100644
--- a/man/systemd.timer.xml
+++ b/man/systemd.timer.xml
@@ -141,7 +141,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
@@ -163,7 +163,14 @@
to any of these options, the list of
timers is reset, and all prior
assignments will have no
- effect.
+ effect.
+
+ Note that timers do not
+ necessarily expire at the precise
+ time configured with these settings,
+ as they are subject to the
+ AccuracySec=
+ setting below.
@@ -171,16 +178,61 @@
OnCalendar=
Defines realtime
- (i.e. wallclock) timers via calendar
+ (i.e. wallclock) timers with calendar
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.
+ related settings.
+
+ Note that timers do not
+ necessarily expire at the precise
+ time configured with this setting,
+ as it is subject to the
+ AccuracySec=
+ setting below.
+
+ AccuracySec=
+
+ Specify the accuracy
+ the timer shall elapse with. Defaults
+ to 1min. The timer is scheduled to
+ elapse within a time window starting
+ with the time specified in
+ OnCalendar=,
+ OnActiveSec=,
+ OnBootSec=,
+ OnStartupSec=,
+ OnUnitActiveSec= or
+ OnUnitInactiveSec=
+ and ending the time configured with
+ AccuracySec=
+ later. Within this time window, the
+ expiry time will be placed at a
+ host-specific, randomized but stable
+ 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
+ 1us. Note that the timer is still
+ subject to the timer slack configured
+ via
+ systemd-system.conf5's
+ TimerSlackNSec=
+ setting. See
+ prctl2
+ for details. To optimize power
+ consumption, make sure to set this
+ value as high as possible and as low
+ as necessary.
+
Unit=
@@ -197,6 +249,45 @@
are named identically, except for the
suffix.
+
+
+
+ Persistent=
+
+ Takes a boolean
+ argument. If true the service unit is
+ immediately triggered when the timer
+ unit is activated and the timer
+ elapsed at least once since the last
+ time the service unit has been
+ triggered by the timer unit. The time
+ when the service unit was last
+ triggered is stored on disk. This is
+ useful to catch up for missed timers
+ when a machine is shutdown temporarily
+ and then is powered up again. 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.
+
@@ -208,7 +299,9 @@
systemd.unit5,
systemd.service5,
systemd.time7,
- systemd.directives7
+ systemd.directives7,
+ systemd-system.conf5,
+ prctl2