Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1124

Summary: problem with SIGCHLD signal handling in vixie-cron
Product: [Retired] Red Hat Linux Reporter: Gilles Detillieux <grdetil>
Component: vixie-cronAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0   
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: 2001-04-10 22:03:38 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 Gilles Detillieux 1999-02-11 23:55:19 UTC 
There is a problem with SIGCHLD signal handling in
vixie-cron version 3.0.1, releases 19 through 24, on
Red Hat Linux 5.0 & 5.1.  This can cause problems with
cron jobs that are run from bash, which doesn't reset
the signal action to SIG_DFL when it's set to SIG_IGN.
Programs that expect normal SIGCHLD handling can fail
in cron jobs.  An example is programs that use popen(),
and check the result of pclose() - it fails with ECHILD.
The htmerge program in ht://Dig fails quite consistently
when run from a cron job on 5.0 or 5.1.

This bug is fixed in vixie-cron-3.0.1-26.src.rpm, in
Red Hat 5.2.  However, no mention is made of this in
the errata for 5.0 and 5.1, and no update RPMs have
been issued for these systems.  This is a frequent source
of confusion and frustration for Red Hat 5.0 and 5.1 users.