docs/130238: nfs.lockd man page doesn't mention NFSLOCKD option or nfslockd module
Vivek Khera
khera at kcilink.com
Tue Jan 6 17:10:02 UTC 2009
>Number: 130238
>Category: docs
>Synopsis: nfs.lockd man page doesn't mention NFSLOCKD option or nfslockd module
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Jan 06 17:10:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Vivek Khera
>Release: FreeBSD 6.4-RELEASE-p1 i386
>Organization:
>Environment:
System: FreeBSD vk-dev.int.kcilink.com 6.4-RELEASE-p1 FreeBSD 6.4-RELEASE-p1 #2: Tue Jan 6 11:21:36 EST 2009 khera at mailerstats.int.kcilink.com:/amd/yertle/u/yertle1/sources/usr6/obj.i386/amd/yertle/u/yertle1/sources/usr6/src/sys/KCI32 i386
>Description:
I upgraded a system (with a custom kernel) from 6.3-REL to 6.4-REL and on
reboot the nfs.lockd program reported the following warning:
Can't find or load kernel support for rpc.lockd - using non-kernel
implementation
The man page doesn't indicate how to correct this problem.
This same issue seems to apply to 7.1-REL also.
>How-To-Repeat:
Build a custom kernel that doesn't build the nfslockd module nor enable the
NFSLOCKD kernel option and run rpc.lockd.
>Fix:
Add a note to the rpc.lockd man page recommending to enable the NFSLOCKD
kernel option, or build the nfslockd kernel module.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-doc
mailing list