Red Hat Bugzilla – Bug 79981
nfslock init always OK for statd even when that is not the case.
Last modified: 2007-11-30 17:06:52 EST
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):
Steps to Reproduce:
Created attachment 88798 [details]
Creates pipe between parent and child so correct status can be returned to rc init script
Created attachment 89217 [details]
Statd now correctly reports is startup status during boots
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.