ntpd on -current 8 hours off

2007-01-26 Thread Stephan A. Rickauer
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,

-- 

 Stephan A. Rickauer

 ---
 Institute of Neuroinformatics Tel  +41 44 635 30 50
 University / ETH Zurich   Sec  +41 44 635 30 52
 Winterthurerstrasse 190   Fax  +41 44 635 30 53
 CH-8057 ZurichWeb  www.ini.unizh.ch

 RSA public key:  https://www.ini.uzh.ch/~stephan/pubkey.asc
 ---



Re: ntpd on -current 8 hours off

2007-01-26 Thread scorch
On Fri, Jan 26, 2007 at 09:30:49AM +0100, 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?

seems more like your TZ is off after upgrade perhaps to US timezone.

a+
scorch



Re: ntpd on -current 8 hours off

2007-01-26 Thread Claudio Jeker
On Fri, Jan 26, 2007 at 09:30:49AM +0100, 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
  ^^^

You're in CET not MST change /etc/localtime to point to
/usr/share/zoneinfo/Europe/Zurich and your problem is fixed.


-- 
:wq Claudio



Re: ntpd on -current 8 hours off

2007-01-26 Thread Fred Crowson

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



Re: ntpd on -current 8 hours off

2007-01-26 Thread Henning Brauer
* Stephan A. Rickauer [EMAIL PROTECTED] [2007-01-26 09:43]:
 on a current snapshot from last week ntpd -s will successfully
 synchronize the clock at once, but 8 hours off the real time.

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

last time I checked switzerland was in MEZ, not MST :)

-- 
Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED]
BS Web Services, http://bsws.de
Full-Service ISP - Secure Hosting, Mail and DNS Services
Dedicated Servers, Rootservers, Application Hosting - Hamburg  Amsterdam



Re: ntpd on -current 8 hours off

2007-01-26 Thread Stephan A. Rickauer
Claudio Jeker wrote:
 On Fri, Jan 26, 2007 at 09:30:49AM +0100, 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
   ^^^
 
 You're in CET not MST change /etc/localtime to point to
 /usr/share/zoneinfo/Europe/Zurich and your problem is fixed.
 
 

stupid me, thanks.

-- 

 Stephan A. Rickauer

 ---
 Institute of Neuroinformatics Tel  +41 44 635 30 50
 University / ETH Zurich   Sec  +41 44 635 30 52
 Winterthurerstrasse 190   Fax  +41 44 635 30 53
 CH-8057 ZurichWeb  www.ini.unizh.ch

 RSA public key:  https://www.ini.uzh.ch/~stephan/pubkey.asc
 ---