Stephan A. Rickauer wrote:
on a current snapshot from last week "ntpd -s" will successfully
synchronize the clock at once, but 8 hours off the real time.
4.0-release and older snapshots behave as expected. Is there some new
'feature' I need to learn about?

# uname -a
OpenBSD arwen.dmz.ini.uzh.ch 4.0 GENERIC#1350 i386

# grep ntpd /var/log/daemon
Jan 26 01:12:50 arwen ntpd[18084]: ntp engine ready
Jan 26 01:14:52 arwen ntpd[30119]: peer 1x0.xx.x.xx now valid
Jan 26 01:15:41 arwen ntpd[14197]: adjusting local clock by 0.157485s
Jan 26 01:19:25 arwen ntpd[30119]: clock is now synced

# date
Fri Jan 26 01:27:33 MST 2007

(on other synchronized machines and on my wrist the time is 09:27:33)


Thanks,

Hi

MST is Mountain Standard Time which would probably explain the time difference, as it is 8 hours behind CET.

Change your /etc/localtime to point to the correct timezone in /usr/local/share/zoneinfo/

HTH

Fred
--
http://www.crowsons.net/puters/zaurus.php

Reply via email to