shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00
Code

man: document how calendar times catch up after system suspend/hibernation

Browse Source 
Fixes: #26166
This commit is contained in:
Lennart Poettering 2023-06-08 10:33:36 +02:00 committed by Luca Boccassi
parent 29de4eba1c
commit 438874cb10
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
man/systemd.timer.xml
View File

@ -209,7 +209,16 @@
adjusted to a network time source <emphasis>before</emphasis> the timer event is set up. Timer units
with at least one <varname>OnCalendar=</varname> expression are automatically ordered after
<filename>time-sync.target</filename>, which <filename>systemd-time-wait-sync.service</filename> is
ordered before.</para></listitem>
ordered before.</para>
<para>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 continously sleeping the timer will only result in a single service activation. If
<varname>WakeSystem=</varname> (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's hardware supports
time-triggered wake-up functionality).</para></listitem>
</varlistentry>
<varlistentry>