Bug 130629

Summary:	initlog returns spurious error status when starting certain daemons
Product:	[Fedora] Fedora	Reporter:	Eric Raymond <esr>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED WORKSFORME	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2	CC:	hklein, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://gpsd.berlios.de/
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-31 21:51:36 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 Eric Raymond 2004-08-23 03:45:27 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
While crafting init scripts for gpsd-2, I found that initlog 
consistently returns a spurious nonzero status when starting up 
gpsd.  The result is that the daemon function displays a FAILED
indication even though daemon startup was successful.




Version-Release number of selected component (if applicable):
initscripts-7.55.1

How reproducible:
Always

Steps to Reproduce:
1. Download and build gpsd from http://gpsd.berlios.de/
2. Run "initlog -q -c 'qpsd'; echo $?" as root.
3. Observe that the return status is nonzero.
4. Verify with ps ax that gpsd is running
    

Actual Results:  The daemon function spuriously indicated failure.


Expected Results:  A big green SUCCEEDED.


Additional info:

I am almost certain this symptom is related to bug #67232.  gpsd
forks itself after it starts up.  I compiled initscripts from 
current CVS HEAD, went in with gdb, and verified that the problem does
indeed appear to be in the waitpid() call in monitor().

Fix the damn SIGCHLD problem already.  Alan Cox diagnosed this one
two years ago.

Comment 1 Bill Nottingham 2005-03-31 21:51:36 UTC

Can't reproduce this on a current release. Note that initlog is deprecated and
will be removed from future releases.