On Tue, 2015-09-29 at 08:36 +0100, Richard W.M. Jones wrote: > On Tue, Sep 29, 2015 at 08:34:44AM +0100, Richard W.M. Jones wrote: > > But anyway as systemd-timesyncd was pointed out in the other reply, > > and it seems to be doing mostly the same as your technique, I guess > > we > > need to find out if we can use that (probably it's just a matter of > > enabling the service?). systemd has a mailing list: > > > > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > I read your other reply now about systemd-timesyncd running too late. > I've tried F23 Beta on my Raspberry Pi, and systemd-timesyncd works fine now. It detects the clock rewind, and resets it. I did try to get a Changelog between F21 and F23 for systemd-timesyncd to try and find what changed, but I can't. I was going to upgrade anyway, but the reason I did it during Beta, was that the sd-card in the Pi popped. So I can't go back to F21 and confirm or diagnose the problem. It might be a good idea in Arm remixes to prefer systemd-timesyncd to chronyd for this reason. Or try chronyd with -s. _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
