Hi Dave and all Il 11/10/2011 21:17, Dave Hart ha scritto: > I suspect not,
I had some IRC chat yesterday (my post was on hold for a while, and I was too curious to wait :) In short, mlichvar thinks I hit bug 1671, which was fixed in 4.2.7 and should therefore be fixed in the next stable release. Do you agree? > my guess is something changed in the network to reduce > the delay. Not sure, it could be... > Assuming you are not using "broadcastdelay" in your > ntp.conf, I am not. > each multicast client association starts off with a unicast > "volley" which measures the unicast and broadcast round-trip delay and > stores the difference to correct future broadcast/multicast delays for > that association. ntpd must be restarted to go through the dance > again to pick up changes in the network unicast and broadcast latency. OK, thanks. I never realized that, in multicast mode, delays were "fixed" after the volley. > FYI, if you were to use manycastclient instead of multicastclient, > you'd preserve the automatic server discovery while each client would > be using unicast exchanges with the server, where the delay is > determined with each exchange independently, insulating against > network changes. Thanks. Manycast is for sure something I want to try. But I want to re-read the NTP docs first ;) It's such a long time since I did it last time, that I am far too much behind! Ciao -- bronto _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
