[Pm-utils] [PATCH 8/8] pm-utils 1.2.3 proposed patches
victor.lowther at gmail.com
Sun Nov 30 16:00:05 PST 2008
On Sun, 2008-11-30 at 14:48 -0800, Dan Nicholson wrote:
> Yeah, I think the only actual "refresh now" method is to kill ntpd and
> then run ntpdate or `ntpd -q', which will block until the clock is
> synchronized. Just starting ntpd does not immediately sync, so
> stopping and restarting ntpd provides no gain over just leaving it
> running. However, if the distro's ntpd initscript syncs first via one
> of the above methods, then I guess people lose that functionality.
Fedora's does not, FWIW. I never had it installed in Debian.
> I was also perusing the ntp-questions archives, and it doesn't appear
> that there's any guarantee that ntpd will synchronize in a reasonable
> amount of time.
> >> > Since we don't, it may be best to drop this hook, just let ntpd continue to
> >> > sync according to its internal schedule, and consider getting networkmanager
> >> > to kick ntpd for us whenever the internet is back up.
> >> I think ultimately that this can only be handled correctly by the
> >> system's networking subsystem since it actually knows when the network
> >> is coming and going. For the common case of NM, it's a trivial
> >> dispatcher script. That assumes that manually restarting ntpd is
> >> necessary.
> > According to my not at all rigorous testing, ntpd continues to operate
> > just fine when the network interfaces appear and disappear. I think we
> > can safely get rid of this hook for now.
> I'm gonna send a message to the ntp-questions list and see if I can
> get a qualified person's opinion.
Well, I have already nuked the hook from my local repo -- given the
above information it seemed more like waving a rubber chicken to fix a
problem that probably didn't exist anyways. Resyncing the date would be
much better handled by a NM dispatch script (or the distro equivlaent)
in any case.
More information about the Pm-utils