Red Hat Bugzilla – Bug 154031
Should report error and not run if prior cron.daily/monthly/etc is still running.
Last modified: 2007-11-30 17:11:03 EST
Description of problem:
We've been running into problems where scripts in cron.daily are hanging. This
can result cases where you have multiple instances of cron.daily running. It
would be useful if there was a pidfile and if valid that cron.daily aborted with
an error to alert the administrator.
This possibly could tie into a solution for bug #150228.
Version-Release number of selected component (if applicable):
I'm currently working on an enhancement that will provide a per-job cron option
or cron job syntax to run jobs "exclusively" - ie. not to run the next scheduled
instance of a job if the previous instance of the same job is still running.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Jason - I'm starting to see messages like:
anacron: Cannot run - another anacron process is already running.: Resource
but I've only seen it for anacron. Is it also in place for the normal crons?
(Please note that FC4 is entering legacy status in a few weeks.)
Please update your system and try with the latest version of crontabs. Let me know, if the
problem still occurs.
Thanks for cooperation.
Um, I don't see any evidence that there has been an update to crontabs. It
seems like run-parts would need to be updated to use a per directory lock file.
Problem from comment#3 are related with anacron. Try to update on anacron-2.3-
40.fc5 and let me know.