Marc Balmer wrote:
* riwanlky wrote:
Hai all,
I have problem on clock with Alic3 board from Pc Engines on OpenBSD 4.3
dmesg->
OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008
and the ntpd message on tail /var/log/daemon
Jul 17 16:14:44 pceng4 ntpd[5847]: adjusting local clock by 86915.408347s
Jul 17 16:18:00 pceng4 ntpd[5847]: adjusting local clock by 86914.457013s
Jul 17 16:20:37 pceng4 ntpd[5847]: adjusting local clock by 86913.683080s
Jul 17 16:21:46 pceng4 ntpd[5847]: adjusting local clock by 86913.389878s
Jul 17 16:26:04 pceng4 ntpd[5847]: adjusting local clock by 86912.104979s
Jul 17 16:26:33 pceng4 ntpd[5847]: adjusting local clock by 86911.965071s
Jul 17 16:27:03 pceng4 ntpd[5847]: adjusting local clock by 86911.859542s
Jul 17 16:31:19 pceng4 ntpd[5847]: adjusting local clock by 86910.603973s
Jul 17 16:33:26 pceng4 ntpd[5847]: adjusting local clock by 86910.009693s
Jul 17 16:37:10 pceng4 ntpd[5847]: adjusting local clock by 86908.914398s
and possible configuration error?
not an error, but you might want to start ntpd with the -s option.
put 'ntpd_flags=-s' into your /etc/rc.conf.local file.
True. A little addition for the archives (since it's been a while now):
$ date -r 86908
Fri Jan 2 01:08:28 CET 1970
This would mean your clock is about 1 hour and 8 minutes off, but is
slowly (as expected) working to reduce the clock skew (while noting the
difference in your log every time). Marc's suggestion would make the
clock take a big leap on next reboot and voila - problem solved (unless
you system is very sensitive about timing, in which case you'd just hav
to wait a few months for the clock to adjust).
If you find the log entries confusing, go read the archives (might be a
few years back from now), but PLEASE do NOT make any suggestion about
changing the wording in the logs. It was beaten to death (or at least I
really REALLY hope it's dead). So please. Don't.
Cheers
/Alexander
