From owner-freebsd-doc@FreeBSD.ORG Tue Jan 6 17:10:01 2009 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF0011065670 for ; Tue, 6 Jan 2009 17:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CE9AF8FC17 for ; Tue, 6 Jan 2009 17:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n06HA14F090726 for ; Tue, 6 Jan 2009 17:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n06HA1ZB090725; Tue, 6 Jan 2009 17:10:01 GMT (envelope-from gnats) Resent-Date: Tue, 6 Jan 2009 17:10:01 GMT Resent-Message-Id: <200901061710.n06HA1ZB090725@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Vivek Khera Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F4C5106567D for ; Tue, 6 Jan 2009 17:01:17 +0000 (UTC) (envelope-from khera@kcilink.com) Received: from yertle.kcilink.com (thingy.kcilink.com [74.92.149.59]) by mx1.freebsd.org (Postfix) with ESMTP id 099708FC22 for ; Tue, 6 Jan 2009 17:01:16 +0000 (UTC) (envelope-from khera@kcilink.com) Received: by yertle.kcilink.com (Postfix, from userid 1002) id 6D54E8A283; Tue, 6 Jan 2009 11:42:02 -0500 (EST) Message-Id: <20090106164202.6D54E8A283@yertle.kcilink.com> Date: Tue, 6 Jan 2009 11:42:02 -0500 (EST) From: Vivek Khera To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: docs/130238: nfs.lockd man page doesn't mention NFSLOCKD option or nfslockd module X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vivek Khera List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2009 17:10:02 -0000 >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@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: