Chris Albertson wrote:
On Wed, Jul 6, 2011 at 8:41 AM, <[email protected]> wrote:
Thank you for your answer, but can this limit be specified in the config
file or command line, please?
I found it.
http://www.eecis.udel.edu/~mills/ntp/html/clock.html
Looks like I was wrong. From my read of the above 2 minutes is under
the "panic" limit and NTP should attempt to correct the offset. It
will "step" the clock in jumps of 125 milliseconds. So it would
take 1,000 steps to correct a 2 minute offset. So take a look every
For a persistent offset of more than 128ms, ntpd will remove the whole
offset in one go. This will be after the 15 minute delay and
subsequently finding multiple samples showing an acceptably low jitter.
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
