Ubuntu
ntp package

on-boot ntpdate should background itself

Bug #16426 reported by Trent Lloyd on 2005-04-25

Affects		Status	Importance	Assigned to	Milestone
	ntp (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

When ntpdate runs to synchronize the clock, it should background itself.

This is because if there is a default route that has no internet connectivity
(or it is broken, or really slow) then it can delay the boot process by quite a
while (30-60s sometimes)

Revision history for this message

Matt Zimmerman (mdz) wrote on 2005-05-03:

The time is set synchronously in order to avoid having the clock change
drastically and unexpectedly later in the boot process (which can confuse programs)

Revision history for this message

Trent Lloyd (lathiat) wrote on 2005-05-03:

Right, I thought this might be the case, perhaps it should timeout faster?

Or maybe the ntpdate feature of slowly skewing the time into sync could be usefull.

Revision history for this message

Christian Reis (kiko) wrote on 2005-06-29:

Bug 18540 is related -- pppd is brought up after ntpdate is run.

Revision history for this message

Christian Reis (kiko) wrote on 2005-06-29:

<mdz> kiko: the right approach is for it to be called when the network interface
is brought up, and not by init at all
<kiko> mdz, doesn't that invalidate your comment
https://bugzilla.ubuntu.com/show_bug.cgi?id=10126#c1
<mdz> kiko: no, ip-up.d is still run synchronously