On 12/15/2011 10:32 AM, Steve Kostecke wrote:
On 2011-12-15, Charles Elliott<[email protected]> wrote:
has the authentication in place to allow it to be added on the fly,
the biggest hit to the time will be that from stopping and starting
ntpd, to change the configuration.
So true! Are there simple instructions somewhere to allow one to
setup NTPD so that ntpq.exe or ntpdc.exe can be used to change the
configuration on the fly, or can someone just post a few lines here to
tell how to do it?
There is no "hit" involved in a warm restart of a stable ntpd.
Anyone claiming otherwise is spreading FUD.
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!
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
