sorry - the timeout value is actually in seconds, so that should be -t
120, not -t 1200.
--
ntpdate runs to early in boot process
https://bugs.launchpad.net/bugs/328936
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Thank you for taking the time to report this issue and help to improve
Ubuntu.
I am closing this report as invalid, because it is not reasonable for
ntpdate (and the various other packages which hook into /etc/network/if-
up.d) to attempt to work around external network delays when the network
is
The /etc/network/if-up.d/ntpdate script could have a ping test to see if the
network is up.
Think that upstart can run deferred scripts, if so this would be a good
solution for ntpdate.
--
ntpdate runs to early in boot process
https://bugs.launchpad.net/bugs/328936
You received this bug notifica
** Description changed:
Binary package hint: ntp
ntpdate 1:4.2.4p4+dfsg-6ubuntu2.2
Only use ntpdate, no ntp daemon running.
It is run from /etc/network/if-up.d
Using IP name log is can't find host, so DNS is not yet up
Using IP address log is no server for sync found, so network not
** Description changed:
Binary package hint: ntp
ntpdate 1:4.2.4p4+dfsg-6ubuntu2.2
Only use ntpdate, no ntp daemon running.
It is run from /etc/network/if-up.d
Using IP name log is can't find host, so DNS is not yet up
Using IP address log is no server for sync found, so network not
