|Summary:||persistent timers does not honour whether job was finished|
|Product:||systemd||Reporter:||Alexandre Detiste <alexandre>|
|Status:||NEW ---||QA Contact:||systemd-bugs|
|i915 platform:||i915 features:|
Description Alexandre Detiste 2014-10-22 10:20:56 UTC
If a lenghty weekly/monthly/yearly persistent job is aborted by a shutdown, it will not be restarted on next reboot. As someone with an SQL background, I mean it would be nice if there was an option to 'ROLLBACK' the timer stamp in /var/lib/systemd/timers/stamp-####.timer to its previous value if the job is aborted by systemd. https://github.com/systemd-cron/systemd-cron/issues/12
Comment 1 Marc Haber 2015-05-01 11:32:06 UTC
Or, as an alternative, only update the timestamp when a job has successfully finished.