Rick Moen <[email protected]> writes: > Quoting Trent W. Buck ([email protected]): > >> If you have systemd, and you don't need to be an NTP *server*, >> consider "systemctl enable systemd-timesyncd" instead. >> This is installed but off by default in Debian 8; >> AIUI it will be the default in Debian 9. > > *cough* Yes, stretch does indeed have this enabled by default. > On new systems, I'm inclining towards openntpd, http://www.openntpd.org/ . > > Of course, this is for the use-case of wanting to have a functional > ongoing ntp daemon,
Fair enough. It sounds like your use case is different from the OP's. > not just a Microsoft-style SNTP client with no error checking, > authentication, no tracking of jitter or delay, no ability to consult > more than one NTP server, and no precaution against adjusting the time > jumps backwards, which is what systemd-timesyncd is. Erm, as at v215 at least some of that appears to be false. /etc/systemd/timesyncd.conf's variable is "Servers" not "Server", though I can't find timesyncd.conf.5 to tell me why. I see logs like this: 2015-10-24T01:34:13+1100 het systemd-timesyncd[265]: Timed out waiting for reply from 10.128.0.1:123 (ntp). 2015-10-24T02:08:21+1100 het systemd-timesyncd[265]: Using NTP server 10.128.0.1:123 (ntp). 2015-10-24T02:08:21+1100 het systemd-timesyncd[265]: interval/delta/delay/jitter/drift 2048s/-0.005s/0.000s/0.008s/-63ppm 2015-10-24T02:42:29+1100 het systemd-timesyncd[265]: interval/delta/delay/jitter/drift 2048s/+0.000s/0.000s/0.007s/-63ppm 2015-10-24T03:16:37+1100 het systemd-timesyncd[265]: interval/delta/delay/jitter/drift 2048s/-0.005s/0.000s/0.003s/-64ppm 2015-10-24T03:50:46+1100 het systemd-timesyncd[265]: interval/delta/delay/jitter/drift 2048s/-0.006s/0.000s/0.004s/-66ppm I can't be arsed RTFSing for more details. _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
