On Sun, 2015-09-27 at 21:53 +0100, Richard W.M. Jones wrote: > On Thu, Sep 24, 2015 at 06:18:24PM +0200, Berend De Schouwer wrote: > > I'm currently using a cron script to touch a file every 10 minutes, > > and > > read that on bootup (before chronyd), and I've added a > > 'Requires=touchClock' to some systemd services. > > I think you don't need the cron script. If you make the > (reasonable?) > assumption that files in /var/log are updated regularly then: > > # find /var/log -type f -print0 | xargs -0 stat -c '%Y %n' /var/log | > sort -nr | head -1 > > (You can omit the %n if you don't care about the actual file that is > the newest).
I think systemd systems are supposed to move to journald. Are there still official /var/log files that are intended to remain over the next few Fedora releases, and guaranteed to exist and updated? I'm not convinced that depending on a wildcard file is robust long- term. It sounds like a recipe for random failures. > I'm don't think depending on journald is right. Journald starts on initrd before the filesystem is mounted, and then moves the journal after / is mounted; so it might be (not confirmed) that /var/log/journal/ has a bad timestamp on boot. > Generally, I think your plan is a good one! I can't claim credit. I got the idea from tedu (BSD). There are no original ideas. > Would be good for my > CubieTruck too. How about trying to get it into systemd upstream? I think we should. Especially since it already ships systemd- timesyncd. How do we go about that? Do I go on the systemd mailing list? OK, away we go... _______________________________________________ arm mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/arm
