Red Hat Bugzilla – Bug 14847
NFS lockd is not stopped properly by init script
Last modified: 2008-05-01 11:37:57 EDT
/etc/rc.d/init.d/nfslock stop never stops NFS' lockd properly, so you
always see a red FAILED indication.
This defect is considered MUST-FIX for Winston Release-Candidate #1
*** Bug 12316 has been marked as a duplicate of this bug. ***
This a kernel problem, unfortunately.
*** Bug 14994 has been marked as a duplicate of this bug. ***
*** Bug 14959 has been marked as a duplicate of this bug. ***
Problem still exists in RC1
Additional verification RC1/TUI Upgrade/Install -- Server still fails.
Getting /etc/rc.d/init.d/functions to wait a little while (udelay 100000) after
sending SIGKILL seems to work around it here. Should lockd catch SIGTERM
*** Bug 16344 has been marked as a duplicate of this bug. ***
Doesnt happen with a standard kernel
Bill, let's implement the workaround Tim found for now, and revert
it if Doug finds the problem in time.
Yes, lockd should catch sigterm, I would think.
The 'not waiting after sigkill is actually a real bug, more
or less. Added in initscripts, will be in 5.47 or so.
Solved by a patch checked into CVS as of 12:30AM, Tue Aug 22, 2000
(Patch29: linux-2.2.16-lockd.patch in the spec file)
Fixed resolution -- "CURRENTRELEASE" would be Red Hat Linux 6.2.
On my dual PII system (only one tested so far), the nfslock shutdown FAILS is
Watch the dates in the notes. I pointed out that the fix was checked into CVS
on 8/22. That's *after* RC2 so obviously the problem *would* still exist in
RC2, so no reason to reopen the bug.