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? (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.) Another question: The documentation says that the timer will trigger "immediately" when it is started. Is this accurate or is there some holdoff time?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
