Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!sdd.hp.com!elroy.jpl.nasa.gov!ames!sgi!shinobu!odin!mitch
From: mitch@sgi.com (Thomas Mitchell)
Newsgroups: comp.sys.sgi
Subject: Re: Can't set time correctly...
Summary: Check also /etc/TIMEZONE
Message-ID: <1990Nov21.015257.12336@odin.corp.sgi.com>
Date: 21 Nov 90 01:52:57 GMT
References: <9010300258.AA10553@mcirps2.med.nyu.edu> <90Oct30.144042est.18958@me.utoronto.ca>
Sender: news@odin.corp.sgi.com (Net News)
Organization: Silicon Graphics Computer Systems,  Mountain View CA. 94039
Lines: 35

In article <90Oct30.144042est.18958@me.utoronto.ca> eastick@me.utoronto.ca (Doug Eastick) writes:
>karron@MCIRPS2.MED.NYU.EDU writes:
>>I give it the correct time(via date or sysadm) and it keeps
>>reporting the time two hours ahead ? I must of done this
>>hundreds of times on dozens of machines, and somthing is wrong someplace
>>with this new machine.
>
>Check if timed is running.  Kill it on all your machines before
>resetting the clocks, then restart it.

Each time I see 'N hours ahead' I look at the environment
variable TZ.  It is most commonly not defining local time
correctly.

It is generaly set by the contents of "/etc/TIMEZONE"

   #ident	"@(#)sadmin:etc/TIMEZONE	1.2"
   #ident	"$Revision: 1.6 $"
   #	Set timezone environment to default for the machine
   TZ=PST8PDT

Looking at the above the systems time zone is set to West
Coast USA time.  Since Irix/Unix (tms) keep internal time to
GMT it is possible that the time is correct but looks wrong.

Users may also set their TZ to match their own notion of
correct.  If you login over wide areas to lots of machines
time can be confusing.

If timed is running you MUST have a valid 'msite' use
"timedc msite" to find it.
--
--
  Thomas P. Mitchell   --  mitch@sgi.com  or mitch%relay.csd@sgi.com
	"All things in moderation; including moderation."