[ntp:questions] Odd (mis)behavior when reference clock fails

Steve Kostecke kostecke at ntp.org
Tue Sep 23 22:32:28 UTC 2008

On 2008-09-23, Unruh <unruh-spam at physics.ubc.ca> wrote:

> That is precisely what ntp is supposed to do for you. 
> Unless you are suggesting that the clock drift is greater than 500PPM.

Unidirectional drift and periodic clock steps are a good indicator that
the clock drift exceeds ntpd's correction capabilities. In these cases
adjusting the tick to bring the clock drift within +/- 500PPM is
sometimes the solution.

As suggested elsewhere in this thread stopping ntpd, deleting the
drift.file, and starting ntpd is another potential solution.

Steve Kostecke <kostecke at ntp.org>
NTP Public Services Project - http://support.ntp.org/

More information about the questions mailing list