Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 79981

Summary: nfslock init always OK for statd even when that is not the case.
Product: Red Hat Enterprise Linux 2.1 Reporter: Steve Dickson <steved>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED ERRATA QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1   
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: 2004-06-15 19:04:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Creates pipe between parent and child so correct status can be returned to rc init script
none
Statd now correctly reports is startup status during boots none

Description Steve Dickson 2002-12-18 12:08:11 UTC
From Bugzilla Helper:
User-Agent: Opera/6.1 (Linux 2.4.18-4GB i686; U)  [en]

Description of problem:
The nfslock rc init script reports that
statd has successfully started which may 
or may not be the case.

The problem lies in the fact there
is no communication between the parent
and child process of statd.  

The statd immediately forks a child process
than exits with successful status. This child
process my or may not startup. If it doesn't start,
all NFS locking (via lockd) will fail (or wores
hang) which could mean different process could hang
or fail at different time making it difficult to debug.


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


How reproducible:
Always

Steps to Reproduce:
1.nfslock start
2.nfslock start
3.
   

Additional info:

Comment 1 Steve Dickson 2002-12-18 21:55:37 UTC
Created attachment 88798 [details]
Creates pipe between parent and child so correct status can be returned to rc init script

Comment 2 Steve Dickson 2003-01-08 18:08:27 UTC
Created attachment 89217 [details]
Statd now correctly reports is startup status during boots

Comment 3 Jay Turner 2004-09-02 02:27:41 UTC
An errata 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-2004-263.html