In article <[EMAIL PROTECTED]>, Spoon <[EMAIL PROTECTED]> 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 claims. Joe Gwinn _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
