"Richard B. Gilbert" <[email protected]> wrote in message
news:[email protected]...
[]
Is this something relatively new? ISTR that it still took about thirty
minutes to get a reasonable facsimile of the correct time even when
restarting with a good drift file.
I wish I could draw a graph here. Since I can't, I'll try to describe
it. Start with an error of twenty or thirty seconds, mad dash to
correct the error, followed by overshoot, and ringing. Ringing decays
slowly. If I were at the controls, I'd be tapping the brakes as we
approach zero error!
I would try a recent NTP with configuration parameters appropriate to the
environment you're using, with a valid drift file. A 20s error should be
corrected by a step, followed by fine adjustments. I'm not talking
microsecond offsets, though.
Cheers,
David
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
