[ntp:questions] Re: where should we update sys_rootdispersion?
duan at cisco.com
Mon Sep 8 19:18:44 UTC 2003
Thanks David for your explanation!
I have a script which has more than ten testcases using the topology I
describe in previous email. I test all kinds of configuration and
combination, server, peer, broadcast, with/without authentication etc.
For each test, I reset clock to a random time on all box to see whether
we are synced or not after some time. Some times offset could be very
very big. Once it is synched, we check whether each peer is reached via
Could somehow ntpd internal state fall into some state (sys_jitter is
very big) because of all the configure/unconfigure, reset clock etc? So
the ntpd just need more time to be sane?
"David L. Mills" wrote:
> Not every arriving packet results in a clock update. The clock filter
> drops some that are older than the best recent packet. These drops are
> revealed in the debug trace and are normal. The increased dispersion is
> well below the cutoff limit.
> I don't know what to tell you. I have duplicated your configuration here
> and everything works gangbusters. You may need to look more closely at
> the debug trace.
> Sorry I can't include your message here; our NNTP server is extremely
> fascist and insists the the quantity of reply exceed the quantity of
> quote. I need to drop a hammer on the maintainer.
More information about the questions