On Fri, 27.06.14 20:45, Michael Biebl ([email protected]) wrote: > Am 27.06.2014 20:10, schrieb Lennart Poettering: > > Well, I know that much. But a service which needs to be restarted on > > cases like this sounds wrong. Thats a hack really. The service should > > just watch time changes and react correctly to that. i.e. use > > TFD_TIMER_CANCEL_ON_SET. THis will report wallclock changes relative to > > monotonic time, which is what you want to watch for this. All system > > resumes will trigger this, of course. > > I might be missing something here, but keep in mind that anacron is not > a long running process. It does its work and then exists. > > So what you describe above does not really help.
Since a long time we had on our TODO list to support timer units that are triggered when the system clock changes, based on TFD_TIMER_CANCEL_ON_SET. Hasn't been implemented yet, should be fairly easy though. This should fit your bill perfectly, no? "OnClockChange=yes" or so... Lennart -- Lennart Poettering, Red Hat _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
