J Moore wrote:
I just installed 3.8 on a Soekris net4801 that's been laying around for
a while (unused, unpowered). I noticed after install that time was off
by like 5 months, so I set it to within a few minutes of current
time/date from the wall clock.
I've been checking the logs, and this is what I'm seeing... this has
been going on for about 8 hours now. Why is ntpd having to make 60+
second adjustments every 3-5 minutes? It would appear the clock on the
Soekris is really BFU.
[...]
Nov 14 06:30:10 opie ntpd[4133]: adjusting local clock by -91.931803s
Nov 14 06:34:22 opie ntpd[4133]: adjusting local clock by -90.983786s
[...]
Nov 14 08:24:20 opie ntpd[4133]: adjusting local clock by -64.294286s
Nov 14 08:27:59 opie ntpd[4133]: adjusting local clock by -63.612736s
OpenNTPd is working as expected. It is using adjtime(2) to skew the
clock, not set it -- in your case, it is slowing it down until it is synced.
Run rdate(8) to speed up the syncing process the hard way (the clock
will jump.) Read up on ntpd(8)'s parameter `-s' in case you ever need to
set a clock that is way off.
Moritz
