My computer (and atd) was started Sat, Oct. 30. On Sun, Oct. 31 03:00 CEST the time was changed to 02:00 CET. On Sunday evening I started an at-job using the command # at 1:20 I expected the job to be started at Mon, Nov. 1 01:20 CET, but it was started at 00:20 CET (= 01:20 CEST). atd is part of at-3.1.8-r9 Reproducible: Always Steps to Reproduce: In contrast to atd vixie-cron took care of DST change
It's worse than that. Even after the daylight savings change has happened, some time specifications can still make at schedule the wrong time. For example: Today is Sun Mar 27, we went back to normal time at 2 am this morning. I try to schedule something for 0005 Tuesday. This does not work: at 0005 tue It actually schedules it for 2305 Monday. This does: at 0005 mar 29 It seems like a deeply rooted error in the way Thomas Koenig's at parses and converts dates to seconds past the epoch.
I've rediscovered this bug today (we went from daylight savings this morning) and it appears to be 3 years old. Is there any chance of fixing it? had upstream been notified?
upstream has a candidate patch at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364975 its a delicate issue however, and at development appears to be slow.
(In reply to Thilo Bangert (RETIRED) (RETIRED) from comment #3) > upstream has a candidate patch at > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364975 > > its a delicate issue however, and at development appears to be slow. Fixed in version at/3.2.2-1 according to that bug. We'll be stabilizing 3.2.5 soon.
