Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 79842 - multiple cron runs when anacron is installed
Summary: multiple cron runs when anacron is installed
Status: RESOLVED DUPLICATE of bug 235174
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal
Assignee: Cron Team
URL:
Whiteboard:
Keywords:
Depends on: 26392
Blocks: 169449
  Show dependency tree
 
Reported: 2005-01-28 07:02 UTC by Neil Darlow
Modified: 2008-10-13 10:51 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Neil Darlow 2005-01-28 07:02:21 UTC
I have anacron and vixie-cron installed in 2004.3.

I have been receiving a number of e-mails at cron.daily run time relating to bzip2 and hard-linking errors during the updatedb run.

On running a ps ax during the cron.daily run, I observed two instances of run-parts cron.daily executing updatedb.

Looking at the header of /usr/sbin/run/parts, there appear to have been some locking and race conditions in the past. It appears there may still be some more unresolve ones.


Reproducible: Sometimes
Steps to Reproduce:
1. Have anacron run at boot
2. Execute a ps ax during the updatedb state
3. Observe multiple instances of run-parts cron.daily and updatedb
Comment 1 Stian Skjelstad 2005-06-27 05:03:14 UTC
It is possible for two occurences of cron to run at once (atleast used to be).
Old servers that I used to maintain having large cronjob-scripts, we always did
locking manually in the script.
Comment 2 BlaisorBlade 2005-07-21 19:30:41 UTC
This depends onto 26392: until that is fixed, this won't work.
Comment 3 BlaisorBlade 2005-11-01 08:17:09 UTC
People, anybody fixing _a bug_? The base bug is trivial to solve (scripts have 
been supplied)... What are you waiting for?
Comment 4 Thilo Bangert (RETIRED) (RETIRED) gentoo-dev 2008-10-13 10:51:00 UTC
well - we reencountered this same problem once again and are working towards a solution on bug #235174. sorry about the gross delay...

*** This bug has been marked as a duplicate of bug 235174 ***