Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 69739 - sys-process/at - atd not aware of daylight savings time changes
Summary: sys-process/at - atd not aware of daylight savings time changes
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Lars Wendler (Polynomial-C)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-01 10:05 UTC by Udo Beckmann
Modified: 2019-03-29 13:07 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Udo Beckmann 2004-11-01 10:05:03 UTC
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
Comment 1 Ken Yap 2005-03-26 23:25:22 UTC
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.
Comment 2 Nick Soveiko 2007-11-04 19:59:41 UTC
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?
Comment 3 Thilo Bangert (RETIRED) (RETIRED) gentoo-dev 2008-06-26 10:32:47 UTC
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.