From: Sergio Luiz Novaes (algol@LCC.UFMG.BR)
Date: Mon Nov 04 2002 - 14:28:32 EST
Just my few cents below,,
Sergio Luiz Novaes
LCC/UFMG - CENAPAD-MG/CO
Tel: +55 31 3499 5391/4910
Fax: +55 31 3499 5390
>Daylight Saving Time is controlled by the TZ variable, set in
>/etc/environment.
>If you search the manual library for TZ you should find the details.
>Double-check
>that it's correct before you go re-setting the time. It's possible to
have
>different TZs for different users - possibly useful if you span time
zones.
>I'd
>expect that to be set in the user's .profile, or similar.
>
>Note that TZ does not cause the clock to be changed. If it's set
correctly,
>the
>clock is always running in UCT, (sort of). TZ is just used by date, cron
>and no
>doubt other things to control how the real time is expressed. This is not
>represented in any log, because it's not really changing anything.
About logs, they are logged or created by applicattion that have access to
TZ variable (every process has access to this variable and will be affected
by it), so they will be impacted by TZ value. Of course the time is UTC
always and TZ just add/subtract your global position from Greenwich but
applications almost always don't use UTC.
>
>I have known NTP to die if it gets too far out of sync; that might have
been
>your
>problem. (It's not really intended to cope with big jumps in time,
although
>I
>thought an hour was OK.) I don't know why it wouldn't have written an
error
>log.
look at /etc/drift.ntp and look the value. If too large (almost 1 hour) I
suppose someone could have changed the time manually to avoid the TZ
problem and this could cause the ntp stop. Look that ntp get syncs with UTC
value, not the real time (TZ changed).
>
>Simon Green
>Philip Morris ITSC Europe
> -----Original Message-----
> From: Dave.Zarnoch@SUNGARD.COM [mailto:Dave.Zarnoch@SUNGARD.COM]
> Sent: 04 November 2002 17:30
> To: aix-l@Princeton.EDU
> Subject: Time reset on servers automagically
>
>
> Folks,
>
> We had a problem with Daylight Savings Time last week.
>
> The system did not automatically reset the time, we did it
> through SMIT.
>
> I know.....I saw the notification not to use SMIT after we used it.
>
> Sometime last week, the time reset itself again to be an hour off.
>
> One of our techs restarted xntpd to run to keep it synced
> until we can get
> a reboot
>
> The question is:
>
> I did not see anything in any of the logs telling me when or
> why the server
> reset the time
> without our intervention.
>
> Is there a process that does some sort of checking and resets?
>
> Also, xntpd died on the servers sometime last week but I did
> not get any
> errors in the logs.
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:18 EDT