From owner-freebsd-questions Fri May 12 4:41:35 2000 Delivered-To: freebsd-questions@freebsd.org Received: from zeppo.it.uu.se (zeppo.it.uu.se [130.238.15.19]) by hub.freebsd.org (Postfix) with ESMTP id 7C3AD37BA3A for ; Fri, 12 May 2000 04:41:30 -0700 (PDT) (envelope-from ertr1013@csd.uu.se) Received: (from ertr1013@localhost) by zeppo.it.uu.se (8.8.5/8.8.5) id NAA24317; Fri, 12 May 2000 13:41:26 +0200 (MET DST) Date: Fri, 12 May 2000 13:41:26 +0200 From: Erik Trulsson To: jpmg@eng.cam.ac.uk Cc: freebsd-questions@FreeBSD.ORG Subject: Re: rpc.lockd / nfs versions Message-ID: <20000512134126.A24219@student.csd.uu.se> References: <200005121127.12482@tulip.eng.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200005121127.12482@tulip.eng.cam.ac.uk>; from jpmg@eng.cam.ac.uk on Fri, May 12, 2000 at 12:27:14PM +0100 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 12, 2000 at 12:27:14PM +0100, jpmg@eng.cam.ac.uk wrote: > On FreeBSD 4.0-RELEASE, rpc.lockd exists, has a man page that suggests it > works, but has a dire warning in /etc/defaults/rc.conf that it doesn't. > > Never one to believe dire warnings, I've tried it. It runs, appears to > try to do things, but fails to work. The test I've been using is the > procmail file locking test suite, which makes some fairly sensible > attempts to see if a particular locking strategy will work. As I understand it it is only a dummy implementation at the moment. So when a client asks for a lock rpc.lockd basically says "Sure, have a lock." and gives a lock to the client without actually locking anything. Therefore it is quite useless for tasks that actually require real locks. What it is useful for is to get semi-broken PC-clients that insist on getting a lock without actually needing it, to work. > > I have a suspicion that the client I was testing from (solaris 2.5.1) > is making a decision to insist on doing 'version==4' locking attempts > _because_ it's noticed that it can do 'version==3' nfs accesses. > > I've come to this conclusion since snooping the network indicates that > the client keeps doing version==4 requests and ignoring the "can't do > that, I'm prepared to accept versions between 1 and 3" reply, whereas > it's quite happy doing locking against a SunOS4 machine where only rpc > versions 1-3 of the lock manager are available, but only nfs v2 is > being provided. > > Is anyone looking at this at the moment? > -- Erik Trulsson ertr1013@student.csd.uu.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message