From owner-freebsd-bugs@FreeBSD.ORG Sat Apr 12 22:00:29 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EBDF37B401 for ; Sat, 12 Apr 2003 22:00:29 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3F1D43FBD for ; Sat, 12 Apr 2003 22:00:28 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h3D50SUp029877 for ; Sat, 12 Apr 2003 22:00:28 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h3D50S1f029875; Sat, 12 Apr 2003 22:00:28 -0700 (PDT) Date: Sat, 12 Apr 2003 22:00:28 -0700 (PDT) Message-Id: <200304130500.h3D50S1f029875@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Bruce Evans Subject: Re: kern/50807: NFS file locking as client deos not working X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bruce Evans List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2003 05:00:29 -0000 The following reply was made to PR kern/50807; it has been noted by GNATS. From: Bruce Evans To: Doug Barton Cc: Shao Zhang , "" Subject: Re: kern/50807: NFS file locking as client deos not working Date: Sun, 13 Apr 2003 14:56:46 +1000 (EST) [Another copy for gnats.] On Sat, 12 Apr 2003, Doug Barton wrote: > > At least for a -current server and client, one or both rpc.lockd and > > rpc.statd enabled here on one or both of the client and server. IIRC, > > enabling both on both works but may be more than necessary. rc.conf.5 > > is very unclear on the exact servers required. > > rpc.statd(8) is much more clear. :) I think it is only clear if you don't need to read it to know what it does. > Both are required. In -current, using > rcNG, you should always get rpc.statd if you ask for rpc.lockd. If that's > not happening, we need to fix the scripts, but I'm pretty sure it is > actually happening. I'll try to remember to double-check this. I use -uncurrent and rc_ng="NO" :-). rc_ng doesn't seem to be any different from rc_og here. There are separate knobs for rpc.lockd and rpc.statd, and both rc.network and rc.d/nfslocking honor the (apparently independent) configured settings for both. Neither rc_ng nor rc_og is fully bug-for-bug compatible with rc.conf.5 which says that these variables are only used for nfs servers. The man page was correct before rev.1.143 of rc.network. Bruce