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 brought up. Structurally, the only sensible design here is for
scripts to assume that the interface being brought up means that the
network is available for use.
I also don't think that synchronizing the clock on a daily basis is
appropriate - users who want their clock to be kept in sync on an
ongoing basis may install the ntp package for this.
Nor does running ntpdate as a "deferred" script adequately address the
problem: the two minute figure you mention is completely arbitrary,
there may be other users for whom that delay is unreasonably long, and
yet others for whom it's too short because their network connection
takes even longer to be brought up.
Finally, if you need the ntpdate script to run with a longer timeout,
then you can configure this by setting NTPOPTIONS="-t 1200" to
/etc/default/ntpdate. (The timeout value is specified in tenths of a
second; so 2*60*10 for 2 minutes.) I think that would be more
appropriate than changing this by default.
** Changed in: ntp (Ubuntu)
Status: New => Invalid
--
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 mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
