[ntp:questions] Bug 2341 - ntpd fails to keep up with clock drift at poll>7
Mischanko, Edward T
Edward.Mischanko at arcelormittal.com
Tue Dec 3 04:16:12 UTC 2013
Yes, it is strange. My point as a software tester, and user, is that if software doesn't work as documented or intended, the why needs to be discovered and addressed with a solution that matches documentation.
From: questions-bounces+edward.mischanko=arcelormittal.com at lists.ntp.org [questions-bounces+edward.mischanko=arcelormittal.com at lists.ntp.org] on behalf of Harlan Stenn [stenn at ntp.org]
Sent: Monday, December 02, 2013 2:10 PM
To: Brian.Inglis at SystematicSw.ab.ca
Cc: questions at lists.ntp.org
Subject: Re: [ntp:questions] Bug 2341 - ntpd fails to keep up with clock drift at poll>7
Brian Inglis writes:
> When I ran current stable under Win 7 with only network servers I
> found I had to drop minpoll to 4 (default is 6) so iburst would
> quickly get a good offset and pull drift down from initial
> out-to-lunch estimate compared to drift file contents.
This is strange - iburst sends its polls at 2 second intervals, and with
a good drift file will sync the clock in about 11 seconds' time.
Dropping minpoll from 6 to 4 should only help if the initial conditions
are "off" enough that the initial iburst volley didn't match up with
things like the stored drift value.
questions mailing list
questions at lists.ntp.org
More information about the questions