XNTPDATE doesn't care about your time zone offset.  You will still need to make the time zone correction, and it is OK to let XNTPDATE run.  When the adjustment in the fall is made, the correction can take a couple of hours to complete, so it probably wouldn't be a good idea for XNTPDATE to run during that time and change the correction value.  In the spring, however, the time change is immediate, so there is nothing to worry about.

-----Original Message-----
From: Jeff Kell [mailto:[log in to unmask]]
Sent: April 01, 2004 11:06 AM
To: [log in to unmask]
Subject: Re: Daylight Savings Time


Gilles Schipper wrote:

> SETCLOCK TIMEZONE=W4:00
>
> Assuming eastern time zone.
>
> You may need to adjust the W4:00 accordingly.
>
> The SHOWCLOCK command will show your exiting TIME ZONE setting.

Umm, I know this would be a stupid un*x/linux question, but for the
3000, running XNTP (scheduled job does ntpdate to our time servers
hourly), what happens?  You still need to set timezone?   Does timezone
have to be 'just right' when ntpdate runs?  Or should I scrap ntpdate
for the weekend and stream the old trustworthy timezone changer job for
2:00 AM Sunday?

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *