So, the one regression I see possible here is on machines with lousy/broken clocks at boot time. If you start ntpd with a clock too far in the past/future, it'll either give up and exit (if VERY far off) or start a drift that could take hours/days to correct. If you remove the restarting around ntpdate, ntpdate will refuse to fix the clock (due to the socket being in use), and you're stuck either with a dead ntpd, or a drift of doom.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593907 Title: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just need to apply it and release a new version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1593907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
