Well, since I didn't install it from source, but a snapshot, I don't have
the northamerica source to get an MD5 # on.

Isn't there some other way to update the zone info files to fix this? 

-----Original Message-----
From: Jonathan Chen [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 28, 2007 1:03 AM
To: Don O'Neil
Cc: freebsd-questions@freebsd.org
Subject: Re: Time changed back to old daylight savings

On Wed, Mar 28, 2007 at 12:45:11AM -0700, Don O'Neil wrote:
> I'm not sure when this happened, but I noticed today that my server 
> reverted back to the old daylight savings time (1 hour off).... When I 
> run ntpdate and have it update it even then it shows the wrong time.

This tends to indicate the your /etc/localtime file is wrong. The
timeservers all return UTC; the display for the date consults /etc/localtime
to display UTC time in local time.

> I haven't done anything to replace the /etc/localtime file, even tried 
> running tzsetup again, but that still didn't help.

This indicates that your zoneinfo files have not been updated correctly.

> At the moment I've addressed the issue with a "date -v +1H".

Which definitely isn't the correct fix.

> Any reason this would happen? How do I fix it?

What does "md5 /usr/src/share/zoneinfo/northamerica" return? (I'm assuming
that you're in North America). On my 6-STABLE machine it's:

 MD5 (/usr/src/share/zoneinfo/northamerica) =

Any other result means that your should re-cvsup, and rebuild your system
again. If it is the same, make sure your zoneinfo files have been rebuilt
(check the file timestamps).

Jonathan Chen <[EMAIL PROTECTED]>                    Once is dumb luck.
                                                 Twice is coincidence.
             Three times and Somebody Is Trying To Tell You Something.

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to