Bug 786113

Summary:	uuidd writes the wrong PID into pidfile
Product:	Red Hat Enterprise Linux 5	Reporter:	Sean E. Millichamp <sean>
Component:	e2fsprogs	Assignee:	Eric Sandeen <esandeen>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	5.7	CC:	sct
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-31 18:18:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sean E. Millichamp 2012-01-31 14:03:05 UTC

Description of problem:

The /etc/init.d/uuidd initscript's status command looks in a pidfile located at /var/lib/libuuid/uuidd.pid (written by the daemon) for the PID to check the status on.

Unfortunately, uuidd seems to write the PID of the original process, and not the PID resulting after the fork operation.  The result is that "/etc/init.d/uuidd status" always returns "uuidd dead but pid file exists".  This causes problems particularly with automated tools that expect the status subcommand to behave properly.

This is a bug fixed upstream at http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=commit;h=cfa30fd554a5ec905ef1e4e3f2b1f8ba9ba8b7e5 and upstream bug tracked at http://sourceforge.net/tracker/?func=detail&aid=1893244&group_id=2406&atid=102406

Comment 1 Eric Sandeen 2012-01-31 18:18:53 UTC

Thanks, this is a dup of bug #707433 and will be fixed in the next possible release.

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