Red Hat Bugzilla – Bug 163141
crond does not explicitly open file descriptor 0 if it is not available while startup
Last modified: 2007-11-30 17:06:54 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Description of problem:
The result of crond not explicitly opening file descriptor 0, is that
the cronjobs inherit a closed fd 0 (stdin), which tends to be an issue
in some cases. eg. anacron invoked from /etc/cron.daily/0anacron fails with error
anacron: Can't close stdin: Bad file descriptor
This issue is same as in bug #145992 reported and fixed against RHEL 3.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Same as in BZ #145992
The patch provided in #145992 (just to address this issue) works fine here.
I don't think this bug warrants an errata update for RHEL-2.1 .
Should customers require that this bug (and MANY others) be fixed, they
should install vixie-cron-4.1-2_EL2, available from:
This is on a CVS branch tag (not the head release) and is built in
It should work in vixie-cron-4.1-2_EL2.
It's inactive one year, so I close it.