Bug 194542 - dmeventd leaves defunct processes around when opened by clvmd
dmeventd leaves defunct processes around when opened by clvmd
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: device-mapper (Show other bugs)
4.0
All Linux
high Severity high
: ---
: ---
Assigned To: Jonathan Earl Brassow
Cluster QE
:
Depends On:
Blocks: 180185 181411
  Show dependency treegraph
 
Reported: 2006-06-08 16:48 EDT by Jonathan Earl Brassow
Modified: 2010-01-11 21:16 EST (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2006-0434
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-08-10 17:25:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jonathan Earl Brassow 2006-06-08 16:48:58 EDT
A proper daemon will reparent itself to init.  This happens if you fork and the
parent exits (amoung other things).  However, clvmd never exits, so when
creating a mirror with clvmd running, a zombie process will be left if you
remove the mirror (or suspend/resume cycles happen).

We need to rewrite the way the daemon is launched.
Comment 2 Jonathan Earl Brassow 2006-06-21 17:28:04 EDT
Waiting for patch to be added to LVM2/device-mapper
Comment 3 Alasdair Kergon 2006-07-04 16:40:39 EDT
The launcher needs fixing to deal with SIGCHILD correctly.
Comment 4 Alasdair Kergon 2006-07-04 16:43:44 EDT
Applying temporary workaround having dmeventd as separate binary.
Comment 10 Red Hat Bugzilla 2006-08-10 17:25:28 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0434.html

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