shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-01-10 05:18:17 +03:00
Code

man: be clearer that .timer time expressions need to be reset to override them

Browse Source 
let's be clearer about the overriding concept for OnCalendar= settings.

Prompted by this thread:

https://lists.freedesktop.org/archives/systemd-devel/2019-March/042351.html
This commit is contained in:
Lennart Poettering 2019-04-01 17:30:45 +02:00
parent 6d463b8aed
commit 58031d99c6
1 changed files with 18 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
man/systemd.timer.xml
View File

@ -142,12 +142,12 @@
</tgroup> </tgroup>
</table> </table>
<para>Multiple directives may be combined of the same and of <para>Multiple directives may be combined of the same and of different types, in which case the timer
different types. For example, by combining unit will trigger whenever any of the specified timer expressions elapse. For example, by combining
<varname>OnBootSec=</varname> and <varname>OnBootSec=</varname> and <varname>OnUnitActiveSec=</varname>, it is possible to define a
<varname>OnUnitActiveSec=</varname>, it is possible to define timer that elapses in regular intervals and activates a specific service each time. Moreover, both
a timer that elapses in regular intervals and activates a monotonic time expressions and <varname>OnCalendar=</varname> calendar expressions may be combined in
specific service each time.</para> the same timer unit.</para>
<para>The arguments to the directives are time spans <para>The arguments to the directives are time spans
configured in seconds. Example: "OnBootSec=50" means 50s after configured in seconds. Example: "OnBootSec=50" means 50s after
@ -162,13 +162,12 @@
and the configured unit is started. This is not the case for and the configured unit is started. This is not the case for
timers defined in the other directives.</para> timers defined in the other directives.</para>
<para>These are monotonic timers, independent of wall-clock <para>These are monotonic timers, independent of wall-clock time and timezones. If the computer is
time and timezones. If the computer is temporarily suspended, temporarily suspended, the monotonic clock pauses, too.</para>
the monotonic clock stops too.</para>
<para>If the empty string is assigned to any of these options, <para>If the empty string is assigned to any of these options, the list of timers is reset (both
the list of timers is reset, and all prior assignments will monotonic timers and <varname>OnCalendar=</varname> timers, see below), and all prior assignments
have no effect.</para> will have no effect.</para>
<para>Note that timers do not necessarily expire at the <para>Note that timers do not necessarily expire at the
precise time configured with these settings, as they are precise time configured with these settings, as they are
@ -192,7 +191,13 @@
the <varname>AccuracySec=</varname> setting the <varname>AccuracySec=</varname> setting
below.</para> below.</para>
<para>May be specified more than once.</para></listitem> <para>May be specified more than once, in which case the timer unit will trigger whenever any of the
specified expressions elapse. Moreover calendar timers and monotonic timers (see above) may be
combined within the same timer unit.</para>
<para>If the empty string is assigned to any of these options, the list of timers is reset (both
<varname>OnCalendar=</varname> timers and monotonic timers, see above), and all prior assignments
will have no effect.</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>