[systemd-devel] [ANNOUNCE] systemd 212

[Lennart Poettering]

On Fri, 28.03.14 10:22, Thomas Bächler (thomas at archlinux.org) wrote:

> Am 26.03.2014 00:28, schrieb Kay Sievers:
> >         * Timer units gained a new Persistent= switch. If enabled
> >           timers configured this way will save to disk when they have
> >           been last triggered. This information is then used on next
> >           reboot to possible execute overdue timer events, that
> >           couldn't take place because the system was powered off. This
> >           enables simple anacron-like behaviour for timer units.
> 
> How do these timers interact with suspending or hibernation? If I
> suspend the system and resume after the timer should have elapsed, the
> timer won't be restarted. Will it still trigger on resume?

Timers are dispatched as soon as systemd is scheduled and the current
time is >= the time configured for the timer. If the system is suspended
for a longer time, and thus systemd doesnt get scheduled then the
dispatching is hnce simply delayed until the next resume.

> (Use-case: A system that rarely reboots and has a timer set daily at
> midnight. The user always suspends the system at 11 and resumes it in
> the morning.)

In that case the timer will be dispatched immediately after resume.

> Another question: The documentation says that the timer will trigger
> "immediately" when it is started. Is this accurate or is there some
> holdoff time?

Immediately is correct.

Lennart

-- 
Lennart Poettering, Red Hat