Laurent, Thank you for your reply.
> I guess that Ubuntu systems with ntp installed would boot a little faster if ntp was not doing useless work by getting started before the network is fully up. That's reasonable, though then this bug should be of low importance I think, as the impact to users is relatively small. > Perhaps, but timesyncd is not activated by default. Ah. I had forgotten before, but now I remember that I was told that timesyncd is automatically deactivated if ntp is installed. > While timesyncd is probably a fine alternative to ntp, this is a bug in ntp and Ubuntu would be a better system with this bug fixed (or ntp removed and timesyncd activated by default). Actually ntp isn't installed by default, and thus I believe that timesyncd is activated by default, but isn't on your system because ntp is installed. I accept that prior to Vivid timesyncd wasn't an option, so it was perfectly reasonable for users to install ntp manually, and then after upgrade if this is broken then that is a bug. But I think the breakage is just the suboptimal attempt to sync time at boot, right? If time with ntp stays synced later without issues, then I'll set Importance to Low on this basis. If I'm wrong in my understanding then we can change this. ** Changed in: ntp (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447142 Title: systemd: ntpdate is started too soon (before the network) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1447142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
