Bug 159441
Summary: | One minute delay updating cron tables | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Patrick Melo <patrick.melo> |
Component: | vixie-cron | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | jn |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:08:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Patrick Melo
2005-06-02 17:57:48 UTC
This is not a bug, but is the way cron works. CRON is not a tool for running programs at specific times - for that purpose, use at(1) . CRON is a tool for running programs at periodic intervals which must not be less than one minute (60 seconds). Every minute, cron runs jobs scheduled for that minute, and then examines its crontab locations for new, deleted or changed crontab files, and loads changed crontab files to contruct its schedule for successive minutes; so the time from making a change to the time the change takes effect will always be at least two minutes. If cron immediately executed newly created schedules every minute, it could not guarantee that at least 60 seconds elapse between job executions, a bug with previous cron versions ( bug #106578 ). An enhanced version of cron is being developed with a more complex scheduling algorithm, which will look at other ways of guaranteeing that at least one minute elapses between job executions while supporting instant job reloading; at the moment, this entails a complete re-design of the way cron works. This version should be ready for RHEL-5 . *** This bug has been marked as a duplicate of 152396 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |