Bug 56436 - Cron ignores some of my jobs
Cron ignores some of my jobs
Product: Red Hat Linux
Classification: Retired
Component: vixie-cron (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Crutcher Dunnavant
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-11-18 07:45 EST by Bernd Bartmann
Modified: 2007-04-18 12:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-11-18 07:47:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
root crontab (706 bytes, text/plain)
2001-11-18 07:45 EST, Bernd Bartmann
no flags Details
excerpt from /var/log/cron for the relavant time frame (1.23 KB, text/plain)
2001-11-18 07:47 EST, Bernd Bartmann
no flags Details

  None (edit)
Description Bernd Bartmann 2001-11-18 07:45:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [de] (X11; U; Linux 2.4.9-13 i686)

Description of problem:
Cron seems to ignore some  of my root cron jobs. I have attached my root
crontab and an excerpt from /va/log/cronlog. The jobs which are scheduled
for 7:03 and 7:05 are never executed. And the job scheduled for 7:02 is
executed at 7:12. The crontab is exactly the same as in my old RedHat 7.0
installation. I never has a problem under RedHat 7.0.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install my crontab
2. watch what jobs are executed

Additional info:
Comment 1 Bernd Bartmann 2001-11-18 07:45:50 EST
Created attachment 37883 [details]
root crontab
Comment 2 Bernd Bartmann 2001-11-18 07:47:12 EST
Created attachment 37884 [details]
excerpt from /var/log/cron for the relavant time frame
Comment 3 Bernd Bartmann 2001-11-18 15:54:20 EST
Sorry guys. This is not a bug. I just found out that a time sync via ntp warped
my system time around 10 minutes forward.

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