Bug 1124 – problem with SIGCHLD signal handling in vixie-cron

This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 1124 - problem with SIGCHLD signal handling in vixie-cron

Summary:	problem with SIGCHLD signal handling in vixie-cron

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	vixie-cron (Show other bugs)
Sub Component:
Version:	5.0
Hardware:	All Linux

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Crutcher Dunnavant
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-02-11 18:55 EST by Gilles Detillieux
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-04-10 18:03:38 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Gilles Detillieux 1999-02-11 18:55:19 EST

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.

Note You need to log in before you can comment on or make changes to this bug.