NTPD unable to adjust local clock
joerg at britannica.bec.de
Wed Apr 6 11:56:47 PDT 2005
On Wed, Apr 06, 2005 at 11:47:47AM -0700, Matthew Dillon wrote:
> What is likely happening is that it is doing one correction every 5
> minutes and since it is not correcting the frequency error the clock
> is sliding out of correction even as the first correction is being
> applied, and then sliding out even worse after the system has finished
> applying the correction. At the next 5 minute mark ntpd applies
> the next correction and the whole mess starts over. You wind up with
> an oscillating clock.
I think I found the reason for the problem. In client_update, it chooses
the offset with the smallest delay for the update, but it doesn't adjust
the offset based on the adjtime it does.
More information about the Users