--- Begin Message ---
Subject: |
Date command bug |
Date: |
Thu, 4 Nov 2010 19:39:36 -0400 |
Hi, I believe I have come across a small bug in the date command when daylight savings time is in the process of being run.
Example:
date --set "7 NOV 2010"
-->Sun Nov 7 00:00:01 EDT 2010
date --date="+1 day"
-->Sun Nov 7 23:00:40 EST 2010
It would appear in Eastern time zone case there is a small 2 hour window of error here whereby the date command has set the zone before it is actually supposed to be set. I have seen this with all time zone shifts. Noticed first last weekend when BST went to GMT.
Could be a known bug.. if so, sorry to trouble you guys.
Best Regards,
Ray
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#7331: Date command bug |
Date: |
Fri, 5 Nov 2010 15:00:47 -0600 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
Raymond Pete wrote:
> Thanks for the info Bob :-) I figured I missed something here.
> I see running my jobs just after midnight is probably not best.
I like running those types of calculations either at 12 noon or using
UTC. Then the DST issues are avoided.
I also like using the 'date -R' format since it is RFC standard (used
in email and news) and unambiguous about timezones. Otherwise I like
using "%F %T %z" for being compact, unambiguous, and sorts nicely.
I will go ahead and close the bug with this email then.
> Appreciate all the work you guys do!
The team enjoys hearing those nice words. :-)
Bob
--- End Message ---