On 21.10.15 18:14, Rick Moen wrote:
Quoting Trent W. Buck (trentbuck(a)gmail.com):
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/
Any specific reason for preferring it over the Debian ntp package?
(I guess familiarity is often a biggie.)
Of course, this is for the use-case of wanting to have
ongoing ntp daemon, 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.
But ... but ... it wouldn't be Fully-Lennarted Systemdix without being
M$-monolithic and M$-degenerate, would it?
One nice thing, if you have a real ntpd running
(ISC's or OpenBSD
Foundation's or Chrony), then systemd-timesyncd quits gracefully (on
systems where I've tested this, at least).
One nice thing, IIUC, is that we can still chuck systemd out, in
favour of real discrete daemons, on install?
And I personally feel much better running a real NTP
After removing networking start from the startup scripts, in favour of
manual networking start, for the few occasions when one is tethered?