[ntp:questions] Getting NTP to correct only the clock skew
joegwinn at comcast.net
Mon Apr 2 12:57:47 UTC 2007
In article <4610f7a8$0$1170$426a74cc at news.free.fr>,
Spoon <devnull at localhost.com> wrote:
> Hal Murray wrote:
> > Spoon wrote:
> >> In my situation, I don't care what time it is, but my clock needs
> >> to tick at the correct rate.
> > How accurate do you need it?
> > You can get "pretty close" if you figure out what the drift
> > should be and use that.
> > You can get that two ways.
> > One is to let ntpd run while connected to the outside world.
> > It will leave the answer in log files and /var/ntp/drift or
> > wherever.
> The problem with that solution is that the frequency offset of the
> system clock changes by a huge amount every time the system reboots.
> cf. thread titled "Clock skew changes drastically between reboots"
Perhaps this was established before, but are the systems having the big
jump over a reboot all equipped with a drifts file? If not, NTP must
relearn the local clock drift rate every time. I would verify the
existence of the drifts file directly, not depending on configuration
More information about the questions