Thanks for the update Robie.  I was not aware of ntpdate being
deprecated (appears to have been deprecated years ago).

For those like myself that require ntpd (the suggested alternative
systemd-timesyncd uses sntp which may not suffice in all use cases), I
think the best fix/workaround is to merely remove the ntpdate package. I
didn't really use ntpdate anymore and suspect it was still installed
from an earlier version of Ubuntu in my case (I've performed a fair
number of inline upgrades on system).

Historically, ntpdate was run prior to starting ntpd in case the clock
was too far off for ntpd to sync.  In looking at the ntp package
further, I see that /etc/default/ntp includes the '-g' option which
allows ntpd to perform a one time sync that would accommodate a clock
with any delta.  This in itself makes ntpdate unneeded for those running
ntp service.  Additionally, ntpd can also be run with arguments to
simulate behavior of ntpdate if needed.

So, if I understand correctly, the ntp package really has no bug (at
least related to starting at boot).  Issue was really due to bug with
deprecated ntpdate package which should be removed if running ntp

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  ntpd not started when using ntpdate

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to