Verified on all four targeted releases: - the hook does no more start a disabled ntp - the hook multiple times does no more is a thundering herd of stop/start ntp - ntpdate does not stop ntp, warp time, start ntp (might warp back if configured differently) - ntpdate no clashing with a (potentially) running ntp is not fatal (there is a log entry of the ntp socket being already in use, but that is correct - one could precheck if running and avoid even trying, but much better than restarting or timewarping)
No regression seen yet, so hopefully all is good. Setting verifications to done. Still if some of the affected could test in addition to that that would be great. ** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial verification-needed-yakkety verification-needed-zesty ** Tags added: verification-done verification-done-trusty verification-done-xenial verification-done-yakkety verification-done-zesty -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
