** Changed in: cron (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) => (unassigned)
** Changed in: cron (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
The Debian maintainer contacted me and mentioned that this bug should be
fixed in Debian unstable. I have performed a merge and uploaded
cron_3.0pl1-113ubuntu1 to our development release (Ubuntu 10.10).
Gary, can you verify if this is fixed in Ubuntu 10.10.
** Changed in: cron (Ubuntu)
Sta
It doesn't seem to be the same, though I don't have an experts-exchange
account to read all the comments.
When I reboot, the problem goes away, cron syncs up to be running at the
correct time according to the system clock. It seems that the problem is
that cron isn't recognising when the system ti
Could it be a "timezones" problem? Can you have a look at this
discussion here:
http://www.experts-
exchange.com/OS/Linux/Distributions/Red_Hat/Q_22977697.html
?
It seems that date and cron do not necessarily see the same time...
--
cron doesn't change schedule when system time is changed
http
I moved the clock back 8 hours. To give the example from my system, I
have a cron job set to run daily at 4am. At ~2am, I set the clock back 8
hours and left the computer running. The job still ran two hours later,
though. After rebooting it ran at the normal time, I didn't check to see
if it would
Hello,
Have you taken into consideration the comments on cron's man file
concerning "hour changes"? I copy from my file below:
"Special considerations exist when the clock is changed by less than 3
hours, for example at the beginning and end of daylight savings time. If
the time has moved forward
