|
|
Posted by Gordon Burditt on 06/24/07 19:47
>> So they have to be adjusted. And even though NTP tries to speed up and
>> slow the clock - it's not perfect. And at times the clock WILL jump
>> forwards or backwards at least one second.
>
>My documentation for NTP proper says it won't do this.
What does happen when the clocks are sync'd, the cluster of systems loses
outside network connectivity to all of its reference clocks, and several
days later, connectivity comes back? adjtime is not perfect and the clocks
will drift without a reference. Eventually that becomes several seconds.
I have seen NTP (running on the system that's supposed to be the
on-site reference, driven from outside references) manage to declare
two reference clocks (stratum 2) and a number of clocks of machines
it locally serves *ALL* falsetickers, and run off of its local clock
(stratum 12) and stay that way for a couple of days until manual
intervention.
>What kind of events are you speaking of that might cause discontinuities?
Navigation:
[Reply to this message]
|