Bug 85321 - persistent timers does not honour whether job was finished
Summary: persistent timers does not honour whether job was finished
Status: NEW
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium minor
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-22 10:20 UTC by Alexandre Detiste
Modified: 2015-05-01 11:32 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.