From owner-freebsd-stable  Tue Sep 19  3:40:50 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65])
	by hub.freebsd.org (Postfix) with ESMTP id 79B0937B422
	for <freebsd-stable@freebsd.org>; Tue, 19 Sep 2000 03:40:44 -0700 (PDT)
Received: (from nobody@localhost)
	by moon.harmonic.co.il (8.9.3/8.9.3) id MAA18629;
	Tue, 19 Sep 2000 12:38:51 +0200
To: Andrew Gordon <arg@arg1.demon.co.uk>
Subject: Re: rpc.lockd
Message-ID: <969359931.39c7423b37dcd@webmail.harmonic.co.il>
Date: Tue, 19 Sep 2000 12:38:51 +0200 (IST)
From: Roman Shterenzon <roman@harmonic.co.il>
Cc: freebsd-stable@freebsd.org
References: <Pine.BSF.4.21.0009181809010.20502-100000@server.arg.sj.co.uk>
In-Reply-To: <Pine.BSF.4.21.0009181809010.20502-100000@server.arg.sj.co.uk>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.0
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Quoting Andrew Gordon <arg@arg1.demon.co.uk>:

> On Mon, 4 Sep 2000, Roman Shterenzon wrote:
> 
> > Hello,
> > The rpc.lockd(8) is marked as broken in /etc/defaults/rc.conf in 4.1-R
> > My question is - how bad is it broken?
> 
> I don't know if anyone already answered this, but here is the answer:
> 
> The rpc.lockd in 4.x simply answers "Yes" to all locking requests, and
> does not maintain any state.  This means that if your programs actually
> need locking, running rpc.lockd will cause problems (file corruption
> etc).
> 
> On the other hand, if your programs don't need locking and are just
> making
> the locking calls for the hell of it, rpc.lockd will allow these
> programs
> to run rather than just hanging up.
> 
> There was talk a few months ago about someone having implemented NFS
> locking properly, but I haven't heard any more since - check the mailing
> list archives.
> 
> [I wrote the existing 'hack' implementation].
> 
Oh my! :(
That's a late reply indeed :(
I use to run it on the new nfs server, because the man page says it's client-side broken.
But now I find out that there's no locks at all.. I just hope that nothing got mixed up..
Perhaps the manpage should reflect this ..ghm.. unexpected behaviour?

--Roman Shterenzon, UNIX System Administrator and Consultant
[ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message