Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 14847 - NFS lockd is not stopped properly by init script
NFS lockd is not stopped properly by init script
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Winston rc1
: 12316 14959 14994 16344 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2000-07-30 11:09 EDT by Jos Vos
Modified: 2008-05-01 11:37 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-23 11:27:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jos Vos 2000-07-30 11:09:46 EDT
/etc/rc.d/init.d/nfslock stop never stops NFS' lockd properly, so you
always see a red FAILED indication.
Comment 1 Glen Foster 2000-07-30 18:09:26 EDT
This defect is considered MUST-FIX for Winston Release-Candidate #1
Comment 2 Glen Foster 2000-07-30 18:27:27 EDT
*** Bug 12316 has been marked as a duplicate of this bug. ***
Comment 3 Bill Nottingham 2000-07-31 10:54:57 EDT
This a kernel problem, unfortunately.
Comment 4 Bill Nottingham 2000-08-01 14:27:51 EDT
*** Bug 14994 has been marked as a duplicate of this bug. ***
Comment 5 Bill Nottingham 2000-08-01 16:27:35 EDT
*** Bug 14959 has been marked as a duplicate of this bug. ***
Comment 6 Jeremy Katz 2000-08-11 16:35:20 EDT
Problem still exists in RC1
Comment 7 Henri Schlereth 2000-08-15 12:28:18 EDT
Additional verification RC1/TUI Upgrade/Install -- Server still fails.
Comment 8 Tim Waugh 2000-08-16 11:15:56 EDT
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
instead though?
Comment 9 Preston Brown 2000-08-16 13:38:57 EDT
*** Bug 16344 has been marked as a duplicate of this bug. ***
Comment 10 Alan Cox 2000-08-16 16:03:15 EDT
Doesnt happen with a standard kernel
Comment 11 Michael K. Johnson 2000-08-20 17:13:29 EDT
Bill, let's implement the workaround Tim found for now, and revert
it if Doug finds the problem in time.
Comment 12 Bill Nottingham 2000-08-21 12:03:28 EDT
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.
Comment 13 Doug Ledford 2000-08-22 00:29:29 EDT
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)
Comment 14 Michael K. Johnson 2000-08-22 09:18:35 EDT
Fixed resolution -- "CURRENTRELEASE" would be Red Hat Linux 6.2.
Comment 15 Gene Czarcinski 2000-08-23 11:27:35 EDT
On my dual PII system (only one tested so far), the nfslock shutdown FAILS is
still there.
Comment 16 Doug Ledford 2000-08-23 11:58:41 EDT
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.

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