By default, machines running Debian Jessie will still be susceptible to
drifting clocks because Jessie's version of systemd is 215-17+deb8u5,
which is behind 219-1. I have confirmed the clock drift (1 second slow)
and also the fix on a vanilla Jessie VM.
$ timedatectl status | grep NTP
NTP enabled: no
NTP synchronized: no
After enabling systemd's NTP daemon:
$ timedatectl set-ntp true
and waiting a bit:
$ timedatectl status | grep NTP
NTP enabled: yes
NTP synchronized: yes
Note that this method has the advantage of not requiring sudo privileges.
To summarize, the options I see are:
- enable systemd's ntp daemon
- install the jessie-backports version of systemd (version 230-7~bpo8+2)
- install a standalone ntp package
Cheers,
Nathaniel
On 09/16/2016 08:00 PM, Nicholas D Steeves wrote:
On Fri, Sep 16, 2016 at 08:55:19PM +0300, Michael Tokarev wrote:
16.09.2016 20:51, Ben Hutchings wrote:
We should install a minimal NTP client by default. Not ntp, it's far
more complex than needed and (partly as a result of that) has a poor
security record.
Systemd comes with systemd-timesyncd these days, JFYI.
Is the addition systemd-timesyncd documented somewhere? 'just
something along the lines of "Simple ntpdate-like time synchronisation
is now provided by systemd". I read the NEWS when upgrading and
didn't notice this change.
Does the laptop task support non-systemd inits? If so,
would there be a benefit to a systemd | ntpdate (or alternative)
dependency for the task?
Cheers,
Nicholas
P.S. Is openntpd the defacto standard these days, for servers?
