On 8/22/2013 11:06, unruh wrote:
What I said was that it is obvioius to you, after the fact, and with the knowledge you have of your system, that the source is the problem. But ntpd is an extremely stupid program, in that it has virtually no memory and must base its decisions on the latest measurement of the offset only. Thus a sudden change in the is taken to mean either a change in the source, or a change in the measurement of the source. In case it is the latter, it changes the computer time only slowly, assuming that measurement errors will average out if you make the change slowly enough.
Right, I know what you said. I'm replying that it would be great if ntpd had a mechanism by which I could give it information that I know about the system so it can make a much more informed decision about a reference clock.
_______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
