bin/107316: [base] [rpc.lockd] nfslocking restart does not restart rpc.lockd

Jonathan Liu Net147 at hotmail.com
Fri Dec 29 04:20:12 PST 2006


>Number:         107316
>Category:       bin
>Synopsis:       [base] [rpc.lockd] nfslocking restart does not restart rpc.lockd
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Dec 29 12:20:11 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Jonathan Liu
>Release:        6.1-SECURITY
>Organization:
>Environment:
FreeBSD freebsd 6.1-SECURITY FreeBSD 6.1-SECURITY #0: Mon Aug 28 05:36:36 UTC 2006     root at builder.daemonology.net:/usr/obj/usr/src/sys/SMP  i386
>Description:
# /etc/rc.d/nfslocking restart
Stopping statd.
Starting statd.

As you can see, restarting nfslocking does only restarts statd when it should restart lockd as well.

This can unexpectedly stop the NFS file locking daemon from working when NFS clients try to use it. This is clearly evident from the output of "rpcbind -p" which doesn't show nlockmgr listed after the restart is complete.
>How-To-Repeat:
# /etc/rc.d/nfslocking restart
>Fix:
Workaround for the moment:
# /etc/rc.d/nfslocking stop
Stopping statd.
Stopping lockd.
# /etc/rc.d/nfslocking start
Starting statd.
Starting lockd.
>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list