Bill Carlson wrote:
On Thu, Feb 08, 2007 at 05:07:33PM -0500, Bates, Bob [CCC-OT_IT] wrote:
I like using the command to display the dates. Depending on what level your
system is, whether the patch is installed, etc. can be discerned from the
output. Right date for change, this one is good. I would get a segment fault
with SP3 and no fix. Wrong dates with SP2 and no fix. Other stuff.
Example:
zdump -v CST6CDT | grep 2007
CST6CDT Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0
gmtoff=-21600
CST6CDT Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1
gmtoff=-18000
CST6CDT Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1
gmtoff=-18000
CST6CDT Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0
gmtoff=-21600
Don't trust just the timezone datafile, make the system prove it's working.
Use date to display the time on 3/12/2007, a correct timezone means the
timezone information is correct.
Example for my systems in Central time:
[EMAIL PROTECTED] ~]$ date -d '2007-03-12'
Mon Mar 12 00:00:00 CDT 2007
A return of:
Mon Mar 12 00:00:00 CST 2007
would indicate the DST change is not effect.
Methinks you need to do better than that to cover for everyone: here,
the know-nothings in government descided that WST meens Western Standard
Time except when it means Western Summer time.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Please do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
