The fix for 246203 was wrong: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/karmic/ntp/karmic/revision/23
The issue is that the ntp init script is started inside the ntpdate ifup script BEFORE the lock file is unlocked. That init script then blocks because the lock is taken. The correct fix is to unlock before starting the init script. The lock is supposed to be shared because both services cannot run at the same time, otherwise one of them will fail to start. ntpd usually wins right now because it gets started more times, but we have encountered a fairly easy to reproduced scenario where ntpdate fails to step the clock at boot, resulting in wildly inaccurate system times. I have attached a patch which fixes the problem here. ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+attachment/4505280/+files/patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125726 Title: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
