Mark Kettenis: > Does this in any way force a write of the drift file or are you > relying on ntpd deciding that it has a better estimate of the > drift somewhere in the next year?
ntpd always updates the drift file when it adjusts the frequency, and it always adjusts the frequency when it is synced. There is no "if (new != old)" check. Also, an old-format drift file is simply too small by a million, i.e., it will essentially set the frequency adjustment to about 0. ntpd will soon recover from that. Hmm, I guess we could skip the compatibility handling completely and just let ntpd re-discover the drift. Starting with an adjustment scaled by 1e-6 is essentially the same as starting with 0 on a newly installed machine. -- Christian "naddy" Weisgerber [email protected]
