Zi Loff <zel...@zeloff.org> wrote: > Is the clock drift just to large for ntpd/adjtime/adjfreq to handle > properly?
I forgot what the maximum is that ntpd can handle, but yes, it looks like the drift is just too large. > If so, is there any 'cure' on the software side? You could try a different kern.timecounter.hardware setting, but on such an old machine there is probably little choice. $ sysctl kern.timecounter.{hardware,choice} Another idea that comes to mind--I've never tried this--is to preload an adjfreq(2) value into /var/db/ntpd.drift. -- Christian "naddy" Weisgerber na...@mips.inka.de