diff options
Diffstat (limited to 'upstream/opensuse-tumbleweed/man5/systemd.timer.5')
| -rw-r--r-- | upstream/opensuse-tumbleweed/man5/systemd.timer.5 | 24 |
1 files changed, 21 insertions, 3 deletions
diff --git a/upstream/opensuse-tumbleweed/man5/systemd.timer.5 b/upstream/opensuse-tumbleweed/man5/systemd.timer.5 index 39a2d662..de75ccde 100644 --- a/upstream/opensuse-tumbleweed/man5/systemd.timer.5 +++ b/upstream/opensuse-tumbleweed/man5/systemd.timer.5 @@ -1,5 +1,5 @@ '\" t -.TH "SYSTEMD\&.TIMER" "5" "" "systemd 254" "systemd.timer" +.TH "SYSTEMD\&.TIMER" "5" "" "systemd 255" "systemd.timer" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -42,8 +42,10 @@ foo\&.service\&. The unit to activate may be controlled by (see below)\&. .PP Note that in case the unit to activate is already active at the time the timer elapses it is not restarted, but simply left running\&. There is no concept of spawning new service instances in this case\&. Due to this, services with -\fIRemainAfterExit=\fR -set (which stay around continuously even after the service\*(Aqs main process exited) are usually not suitable for activation via repetitive timers, as they will only be activated once, and then stay around forever\&. +\fIRemainAfterExit=yes\fR +set (which stay around continuously even after the service\*(Aqs main process exited) are usually not suitable for activation via repetitive timers, as they will only be activated once, and then stay around forever\&. Target units, which by default do not deactivate on their own, can be activated repeatedly by timers by setting +\fIStopWhenUnneeded=yes\fR +on them\&. This will cause a target unit to be stopped immediately after its activation, if it is not a dependency of another running unit\&. .SH "AUTOMATIC DEPENDENCIES" .SS "Implicit Dependencies" .PP @@ -231,6 +233,8 @@ is ordered before\&. When a system is temporarily put to sleep (i\&.e\&. system suspend or hibernation) the realtime clock does not pause\&. When a calendar timer elapses while the system is sleeping it will not be acted on immediately, but once the system is later resumed it will catch up and process all timers that triggered while the system was sleeping\&. Note that if a calendar timer elapsed more than once while the system was continuously sleeping the timer will only result in a single service activation\&. If \fIWakeSystem=\fR (see below) is enabled a calendar time event elapsing while the system is suspended will cause the system to wake up (under the condition the system\*(Aqs hardware supports time\-triggered wake\-up functionality)\&. +.sp +Added in version 197\&. .RE .PP \fIAccuracySec=\fR @@ -255,6 +259,8 @@ for details\&. To optimize power consumption, make sure to set this value as hig Note that this setting is primarily a power saving option that allows coalescing CPU wake\-ups\&. It should not be confused with \fIRandomizedDelaySec=\fR (see below) which adds a random value to the time the timer shall elapse next and whose purpose is the opposite: to stretch elapsing of timer events over a longer period to reduce workload spikes\&. For further details and explanations and how both settings play together, see below\&. +.sp +Added in version 209\&. .RE .PP \fIRandomizedDelaySec=\fR @@ -279,6 +285,8 @@ to 0, thus encouraging coalescing of timer events\&. In order to optimally stret and \fIRandomizedDelaySec=\fR to some higher value\&. +.sp +Added in version 229\&. .RE .PP \fIFixedRandomDelay=\fR @@ -291,12 +299,16 @@ This setting has no effect if \fIRandomizedDelaySec=\fR is set to 0\&. Defaults to \fBfalse\fR\&. +.sp +Added in version 247\&. .RE .PP \fIOnClockChange=\fR, \fIOnTimezoneChange=\fR .RS 4 These options take boolean arguments\&. When true, the service unit will be triggered when the system clock (\fBCLOCK_REALTIME\fR) jumps relative to the monotonic clock (\fBCLOCK_MONOTONIC\fR), or when the local system timezone is modified\&. These options can be used alone or in combination with other timer expressions (see above) within the same timer unit\&. These options default to \fBfalse\fR\&. +.sp +Added in version 242\&. .RE .PP \fIUnit=\fR @@ -317,6 +329,8 @@ Use on the timer unit to remove the timestamp file maintained by this option from disk\&. In particular, use this command before uninstalling a timer unit\&. See \fBsystemctl\fR(1) for details\&. +.sp +Added in version 212\&. .RE .PP \fIWakeSystem=\fR @@ -334,6 +348,8 @@ Note that behaviour of monotonic clock timers (as configured with \fIOnUnitInactiveSec=\fR, see above) is altered depending on this option\&. If false, a monotonic clock is used that is paused during system suspend (\fBCLOCK_MONOTONIC\fR), if true a different monotonic clock is used that continues advancing during system suspend (\fBCLOCK_BOOTTIME\fR), see \fBclock_getres\fR(2) for details\&. +.sp +Added in version 212\&. .RE .PP \fIRemainAfterElapse=\fR @@ -345,6 +361,8 @@ is on, starting the timer a second time has no effect\&. However, if \fIRemainAfterElapse=\fR is off and the timer unit was already unloaded, it can be started again, and thus the service can be triggered multiple times\&. Defaults to \fBtrue\fR\&. +.sp +Added in version 229\&. .RE .PP Check |