Interestingly, on my system (at least the one I tested; SuSE SLES 9
2.6.5-7.283-s390x), I don¹t get the invalid date response:
rockhopper:~ # date
Fri Mar 2 09:33:13 CST 2007
rockhopper:~ # date -d "2007-03-11 1:59 am"
Sun Mar 11 01:59:00 CST 2007
rockhopper:~ # date -d "2007-03-12 1:59 am"
Mon Mar 12 01:59:00 CDT 2007
rockhopper:~ # date -d "2007-03-11 2:01 am"
Sun Mar 11 03:01:00 CDT 2007
rockhopper:~ # date -d "2007-03-11 2:00 am"
Sun Mar 11 03:00:00 CDT 2007
It does shift it correctly to the next hour, though.
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OC-1-13 200 First Street SW
/ ( ) \ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
> From: Bill Carlson <[EMAIL PROTECTED]>
>
> On Thu, Mar 01, 2007 at 03:16:08PM -0800, Fargusson.Alan wrote:
>> How do you test today to see that the time change will occur at 2:00 AM on
>> March 11?
>
> [EMAIL PROTECTED] ~]$ date -d '2007-03-11 03:00:00'
> Sun Mar 11 03:00:00 CDT 2007
>
>
> Note, the date '2007-03-11 02:00' doesn't exist in a timezone observing US
> DST, and date makes note of that:
>
> [EMAIL PROTECTED] ~]$ date -d '2007-03-11 02:00:00'
> date: invalid date `2007-03-11 02:00:00'
>
>
> [EMAIL PROTECTED] ~]$ date -d '2007-03-11 01:59:59'
> Sun Mar 11 01:59:59 CST 2007
>
>
>
> I recommend this over the zdump test, as the ACTUAL system is exercised,
> rather than dumping the data from a file that may not be used.
>
> Finally, remember this is all about timezone display, the actual time in UTC
> does NOT change!
----------------------------------------------------------------------
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
