Alexander Hall wrote:
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

Oops. My bad. A better approach (combined with correct reading):

$ date -ur 0
Thu Jan  1 00:00:00 UTC 1970
$ date -ur 86908
Fri Jan  2 00:08:28 UTC 1970

So that would mean a little more than _one_day_ and eight minutes... No wonder it would take a few months (I was surprised and not at all convinced by my calculations). :-)

/Alexander

Reply via email to