> > > [1]: https://wiki.ubuntu.com/Netplan#Frequently-asked_questions > > Sorry, I completely dropped the ball on this. >
No problem at all, I know there is always one task too mcuh :-) > I have again looked through all the open bugs and I've come to the > conclusion that ntpdate in it's current form is probably impossible to > fix. Also I think that >90% of the current ntpdate users have it > installed for /usr/bin/ntpdate and run a real ntp daemon for timekeeping > purposes. > ack, people either don't need super reliable time (doesn't matter then) or have a real syncing daemon. I've therefor proposed in Bug#908286 to just drop the hooks from ntpdate > and document this in the release notes for Buster. If we build a new > package containing sntp-hooks it should not be pulled in automatically, > even for the current ntpdate users. > TBH - I missed an update here as well I think - maybe I considered this bug a zombie of some sorts. The new bit would be that Ubuntu sort of "gave up" on ntpd anyway. As you say systemd-timesyncd covers it in >95% of the cases and for the "do it better" job there is chrony which is really great. So since Bionic we recommend those instead of the things from the ntpd package. Also there were massive security concerns on ntpd (from the security Team, as maintenance effort on that is disproportional). IMO with systemd-timesyncd available and ntpd dealing quite well with > changing interfaces and temporarily broken connectivity on startup these > days we don't need these triggers anymore. > Yes And for those that totally demand hooks, which with systemd-networkd can be quite hard I brought these upstream :-) https://git.tuxfamily.org/chrony/chrony.git/tree/examples/chrony.nm-dispatcher What do you think? > I agree to dropping the hooks. And I'd further recommend you/Debian to consider systemd-timesyncd (+ chrony if needed) the better recommended ntp options for Buster.
