HP3000-L Archives

April 2003, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Atwood, Tim (DVM)" <[log in to unmask]>
Reply To:
Atwood, Tim (DVM)
Date:
Thu, 3 Apr 2003 16:57:14 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
We were going over our time change procedures. someone came up with
questions about all the different time change methods and parameters and
what they mean. I could not answer some of them. So I come coming to The
Great an Wise HP3000 List....

For years upon years we have automatically run a job on the time change
Sunday at 1:59 AM. Job name "TIMECHG". In the spring this job does:

SETCLOCK TIMEZONE=W07
(Pacific Daylight Time)

For the last couple of years we have also started running an NTP time
synchronization job at 3:00 AM every morning.
/NTP/CURRENT/bin/ntpdate -B <NTP server name>

The TZ variable is set to "PST8PDT"

Now as I understand it, NTP is adjusting the UTC time. But does it also
adjust the timezone? In other words are we duplicating effort with these
jobs? Is TIMECHG setting the time zone to W07:00 only to have NTP find it is
already W07:00?

If we stopped running "TIMECHG" would the NTP command adjust the time zone
from W08:00 to W07:00? Or would it adjust the UTC time without adjusting the
time zone.

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

ATOM RSS1 RSS2