From owner-freebsd-questions Mon Dec 4 9:30:40 2000 From owner-freebsd-questions@FreeBSD.ORG Mon Dec 4 09:30:37 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from kiwi.it.uu.se (kiwi.it.uu.se [130.238.9.168]) by hub.freebsd.org (Postfix) with ESMTP id D807037B400 for ; Mon, 4 Dec 2000 09:30:36 -0800 (PST) Received: (from ertr1013@localhost) by kiwi.it.uu.se (8.8.5/8.8.5) id SAA02895; Mon, 4 Dec 2000 18:30:17 +0100 (MET) Date: Mon, 4 Dec 2000 18:30:17 +0100 From: Erik Trulsson To: Brandon Williams Cc: freebsd-questions@freebsd.org Subject: Re: NFS file locking in 4.2-RELEASE Message-ID: <20001204183017.A2872@student.uu.se> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from drift@sigmatel.com on Mon, Dec 04, 2000 at 11:13:59AM -0600 Sender: ertr1013@csd.uu.se Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 04, 2000 at 11:13:59AM -0600, Brandon Williams wrote: > Hi, > > I apologize if this has been discussed, but I searched the archives and > could not find any mention of it, at least specifically for 4.2. Yes, it has been discussed several times. Both on -questions and on -stable. Search harder next time. > > rpc.lockd does not appear to work when the freebsd box is acting as an nfs > fileserver and a solaris 7 client attempts to lock a file (specifically > with cadence, a CAD app.) > > I realize that in /etc/defaults/rc.conf rpc.lockd is commented as being > broken, but there is not mention of this in the man page, or what, if any, > functionality lockd currently has. It is just a dummy implementation that basically says "Sure, have a lock" whenever an application asks for a lock, but without doing any actual locking. The only reason for using it is if you have an application that insists on getting a lock without really needing it. > > Finding that this does not work is quite depressing to me, as I just > convinced my company to move from a linux 2.4 (yuck) nfs server that was > causing problems, guaranteeing that freebsd would do a much better > job. Unfortunately I'll never get the chance to prove this, as I had to > quickly fall back to the linux system early this morning since file > locking is essential to my users' applications. > -- Erik Trulsson ertr1013@student.uu.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message