Matthew Jarvis wrote:
Bob Miller wrote:
Matthew Jarvis wrote:
That's what I would have thought, but I also don't recall having to
deal with DST as it went on/off...
Better check my OS patches....
Here's the easiest way to check.
$ date --date=3/12/2007
Mon Mar 12 00:00:00 PDT 2007
See where it says "PDT"? This system is up to date.
Revisiting this as time draws near...
My servers here at the office aren't updated with the revised stuff...
however, my offsite webserver is....
Using this URL/thread as a guide:
http://www.linuxquestions.org/questions/showthread.php?t=518752
I seems that one needs to regenerate a file called "EST5EDT" then copy
it into place, implying that it is generic.
Can I just grab the one off the web server that is correct and copy it
to my local servers and just be done with this?
Matthew Jarvis
Question: How accurate do your servers have to be? Is setting them
manually good, or do you have to sync with some time signal?
Assuming manual is OK, all that is required is for the hardware clock to
be set to Univeral time, and then set your TZ environmental variable to
something like: TZ=CST6CDT5,M3.2.0/2,M11.1.0/2
Since you are (probably?) in the Pacific time zone, your line would
read: TZ=PST8PDT7,M3.2.0/2,M11.1.0/2
That traslates as
(1) standard time is known as PST with an offset of 8 hours from
Universal time
(2) alternate time is known as PDT with an offset of 7 hours from
Universal time
(3) alternate time begins at 2:00 AM on the second Sunday of March
(4) alternate time ends at 2:00 AM on the first Sunday of November
... and that is what the new rule says it should do.
If your system supports the file /etc/TIMEZONE, put that line in there
If your system does not support that file, put it in /etc/profile (at
the end of the file), followed by a line that says: export TZ
In either case, reboot your machine to make it take effect.
Hope that helps
Regards
Fred James
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
