Hal Murray wrote: >> Restart ntpd after deleting the drift file. > > I think some version of ndpd used to write out the drift file > when it exited. (Maybe I'm dreaming and that was just a > suggestion for purposes of discussion.) > > So I would do > stop ntpd > delete the drift file > start ntpd > > Then you know it got deleted. > > An alternative would be > delete drift file > restart ntpd > check to make sure drift file is not there >
Yes. And one missing step: After stopping ntpd, "ntpdate -b [server]". The single most common cause of a large negative drift value is a system whose clock has not been initialized before starting ntpd (or has been stopped during a large time adjustment). -Tom _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
