From owner-freebsd-bugs@FreeBSD.ORG  Sat Apr 12 22:45:23 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id F261337B401; Sat, 12 Apr 2003 22:45:22 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A693E43F3F; Sat, 12 Apr 2003 22:45:21 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id OAA22952;
	Sun, 13 Apr 2003 14:54:56 +1000
Date: Sun, 13 Apr 2003 14:54:55 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Doug Barton <DougB@freebsd.org>
In-Reply-To: <200304122230.h3CMU9mu009921@freefall.freebsd.org>
Message-ID: <20030413143620.R5630@gamplex.bde.org>
References: <200304122230.h3CMU9mu009921@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-bugs@freebsd.org
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
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2003 05:45:23 -0000

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