Bug 687946 - at misinterprets times at switch to daylight savings
Summary: at misinterprets times at switch to daylight savings
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: at
Version: 5.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Marcela Mašláňová
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-15 19:21 UTC by Donald Cohen
Modified: 2011-03-16 12:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 12:49:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Donald Cohen 2011-03-15 19:21:59 UTC
Description of problem:
I hope I'm reporting this to the right place - 
 cat /etc/issue =>
 CentOS release 5.4 (Final) ...
I've not done any yum update for a long time, so this might be a fixed
bug, but I don't see it in the list.

Here's the file /root/monitor-load
====
uptime >> /tmp/load-record 
at -f /root/monitor-load now + 5 minutes 2> /dev/null 
====
I start it by putting the second line into a shell.
The output file, /tmp/load-record, includes this:
... one record every 5 minutes until just before the switch to daylight savings time
 01:48:00 up 424 days, 19:19,  1 user,  load average: 0.00, 0.00, 0.00 
 01:53:00 up 424 days, 19:24,  1 user,  load average: 0.00, 0.00, 0.00 
 01:58:00 up 424 days, 19:29,  1 user,  load average: 0.00, 0.00, 0.00 
 01:58:00 up 424 days, 19:29,  1 user,  load average: 0.00, 0.00, 0.00 
 01:58:00 up 424 days, 19:29,  1 user,  load average: 0.00, 0.00, 0.00 
 01:58:00 up 424 days, 19:29,  1 user,  load average: 0.00, 0.00, 0.00 
 01:58:00 up 424 days, 19:29,  1 user,  load average: 0.00, 0.00, 0.00 
 01:58:00 up 424 days, 19:29,  1 user,  load average: 0.00, 0.00, 0.00 
 01:58:00 up 424 days, 19:29,  1 user,  load average: 0.00, 0.00, 0.00 
 01:58:00 up 424 days, 19:29,  1 user,  load average: 0.00, 0.00, 0.00 
and now we seem to be running the job as soon as possible until
 01:59:59 up 424 days, 19:31,  1 user,  load average: 2.23, 0.84, 0.30 
 01:59:59 up 424 days, 19:31,  1 user,  load average: 2.23, 0.84, 0.30 
 01:59:59 up 424 days, 19:31,  1 user,  load average: 2.23, 0.84, 0.30 
 03:00:00 up 424 days, 19:31,  1 user,  load average: 2.23, 0.84, 0.30 
 03:05:00 up 424 days, 19:36,  1 user,  load average: 0.01, 0.30, 0.21 
 03:10:00 up 424 days, 19:41,  1 user,  load average: 0.00, 0.10, 0.14 

I suspect that at 1:58, now + 5 minutes is interpreted as 2:03 and that
in turn is somehow viewed as 1:03, which means run it immediately.


Version-Release number of selected component (if applicable):
How can I tell?

Comment 1 Marcela Mašláňová 2011-03-16 12:49:27 UTC
I'm aware of this issue rhbz#435765, but I didn't find solution yet. It's more probable that it will be fixed in Fedora in future. Imho backport in RHEL is not likely.

Version of component is simple: 'rpm -q at'.


Note You need to log in before you can comment on or make changes to this bug.