[systemd-devel] Calendar Timers: setting system clock may trigger jobs from the past

Tobias Geerinckx-Rice tobias.geerinckx.rice at gmail.com
Mon Aug 4 10:39:07 PDT 2014

On 4 August 2014 14:45, Lennart Poettering <lennart at poettering.net> wrote:
> On Mon, 04.08.14 12:50, Peter Mattern (matternp at arcor.de) wrote:
>> Hello.
>> If a *.timer unit's timestamp as stated by OnCalendar is in the past
>> and the actual system time is even before that timestamp the *.timer
>> gets activated when the system clock gets set.
> This sounds like you should make sure your one-time ntp service should
> be ordered before time-sync.target and your .timer unit after it, so
> that it it doesn't get scheduled before the time is set correctly (in
> fact, on the TODO list there's an item, to make sure that we
> implicitly order all OnCalendar units after time-sync.target, but in the
> meantime you can do that manually).

Hallo all,

I've just sent a simple fix that works for me, albeit on a boring old
desktop system.

(As this is my first systemd patch, feel free to flak me for missing
something obvious.)



More information about the systemd-devel mailing list