I know it's a long time, but I'm cleaning up old NTP bugs atm.
udev is there, by default for a long time - due to that the wait will work
"now".
If we would have such a state we could set this bug "Fix Released long ago"
** Changed in: ntp (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/44166
Title:
No NTP-Sync during bootup if /usr on different filesystem
Status in ntp package in Ubuntu:
Fix Released
Bug description:
During the bootup of Dapper Drake Beta 2 (with all available updates
installed) the /etc/init.d/networking script is called and it
initializes my network interface eth0 correctly. But for some reason
ifup, which is called by the networking script, doesn't execute
/etc/network/if-up.d/ntpdate. I noticed this since, after several
reboots, a timedrift has occured.
The somehow strange part of this bug is, that it only appears during bootup.
If the system is running and I execute
sudo /etc/init.d/networking restart
the ntpdate script gets called and the time gets synced.
I should add that I have a flawless, permanent internet connection, so this
bug is not related to a misconfigured router or NIC configuration. I added the
line
/usr/bin/logger "ntpdate called"
to the ntpd script, to confirm my theory. After a reboot "ntpdate called"
doesnt appear in the logs, but after running /etc/init.d/networking manually it
appears.
This bug was reproduceable on 3 different ubuntu installations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/44166/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
