[pkg-ntp-maintainers] Bug#542602: Bug#542602: moreinfo+retitle

[Kurt Roeckx]

On Fri, Dec 25, 2009 at 09:11:56PM +0100, Holger Levsen wrote:
> retitle 542602 "event based boot system needed to solve use cases"
> thanks
> 
> <h01ger> pere, isnt #417118 solved by dependency booting?
> <pere> h01ger: nope.  it is one of the problems that need event based boot to 
> work.
> <h01ger> when do you expect event base booting in debian? IOW: isnt that 
> something, the user needs to configure?
> <pere> h01ger: with the current rate of fixing the remaining stuff with 
> upstart, in squeeze+1.
> <h01ger> upstart fixes that?
> <pere> upstart make it possible to fix that.  it is a event based boot 
> framework.
> <pere> then ntpdate can run when the network is up and the dns server is 
> available.
> <h01ger> nice
> <pere> h01ger: a similar issue is #542602
> <h01ger> pere, can i quote this in 417118?
> <pere> h01ger: sure.
> <pere> I suspect a workaround would be to have several init.d scripts for 
> ntpdate, all running the program when their time has come. :)

I'm not sure why you send this to this bug.  It's not useful to
wait until ntpd is started, if you want to wait on something
related to ntpd is that it decided it's in a sync state.  And that
can take some time.  If there really are services that want to
wait for that you can use something like ntp-wait.  Upstream also
seem to be working on a --wait-sync option to ntpd itself.

Most services want the time to be more or less correct, for most
an offset of a few seconds will probably not even be a problem.
Maybe it would be useful to also have an "event" for that.  This
is something ntpdate can do now, maybe it would be useful that
ntpd also has such an option?  (Ntpdate will be removed at some
point.)  Maybe $time should be that event.

Anyway, with some event based "boot" thing, it's probably easier
to write something that waits for ntpd to be synchronised.


Kurt