X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.timer.xml;h=518ae2a9f1c55dc44a5b17bb29eb437fbcd773da;hb=7e61bf2019c2cab4e1e21ee775bab25ef1a1bb81;hp=5845383e8bb7b44d6f5b96df9495baf3ba36bf96;hpb=b36b082c8a24d2575909c3e0b4b8aeec49ec17bb;p=elogind.git
diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index 5845383e8..518ae2a9f 100644
--- a/man/systemd.timer.xml
+++ b/man/systemd.timer.xml
@@ -68,14 +68,25 @@
timer specific configuration options are configured in
the [Timer] section.
- For each timer file a matching unit file must
+ For each timer file, a matching unit file must
exist, describing the unit to activate when the timer
- elapses. By default a service by the same name as the
+ elapses. By default, a service by the same name as the
timer (except for the suffix) is activated. Example: a
timer file foo.timer activates a
matching service foo.service. The
unit to activate may be controlled by
Unit= (see below).
+
+ Unless DefaultDependencies=
+ is set to , 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.
@@ -88,36 +99,36 @@
- OnActive=
- OnBootup=
- OnStartup=
- OnUnitActive=
- OnUnitInactive=
+ OnActiveSec=
+ OnBootSec=
+ OnStartupSec=
+ OnUnitActiveSec=
+ OnUnitInactiveSec=Defines timers
relative to different starting points:
- OnActive= defines a
+ OnActiveSec= defines a
timer relative to the moment the timer
itself is
- activated. OnBootup=
+ activated. OnBootSec=
defines a timer relative to when the
machine was booted
- up. OnStartup=
+ up. OnStartupSec=
defines a timer relative to when
systemd was
- started. OnUnitActive=
+ started. OnUnitActiveSec=
defines a timer relative to when the
unit the timer is activating was last
- activated. OnUnitInactive=
+ activated. OnUnitInactiveSec=
defines a timer relative to when the
unit the timer is activating was last
deactivated.Multiple directives may be
- combined, of the same and of different
+ combined of the same and of different
types. For example, by combining
- OnBoot= and
- OnUnitActive= it is
+ OnBootSec= and
+ OnUnitActiveSec= it is
possible to define a timer that
elapses in regular intervals and
activates a specific service each
@@ -125,17 +136,17 @@
The arguments to the directives
are time spans configured in
- seconds. Example: "OnBoot=50" means
+ seconds. Example: "OnBootSec=50" means
50s after boot-up. The argument may
also include time units. Example:
- "OnBoot=5h 30min" means 5 hours and 30
+ "OnBootSec=5h 30min" means 5 hours and 30
minutes after boot-up. For details
about the syntax of time spans see
systemd.unit5.If a timer configured with
- OnBootup= or
- OnStartup= is
+ OnBootSec= or
+ OnStartupSec= is
already in the past when the timer
unit is activated, it will immediately
elapse and the configured unit is
@@ -144,7 +155,7 @@
directives.These are monotonic timers,
- independant of wall-clock time and timezones. If the
+ independent of wall-clock time and timezones. If the
computer is temporarily suspended, the
monotonic clock stops too.
@@ -156,13 +167,13 @@
when this timer elapses. The argument is a
unit name, whose suffix is not
.timer. If not
- specified this value defaults to a
+ specified, this value defaults to a
service that has the same name as the
timer unit, except for the
- suffix. (See above.) It is recommended
+ suffix. (See above.) It is recommended,
that the unit name that is activated
and the unit name of the timer unit
- is chosen identical except for the
+ are named identical, except for the
suffix.
@@ -171,7 +182,7 @@
See Also
- systemd8,
+ systemd1,
systemctl8,
systemd.unit5,
systemd.service5