From owner-freebsd-questions Mon Dec 4 9:15:28 2000 From owner-freebsd-questions@FreeBSD.ORG Mon Dec 4 09:15:26 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mcfeely.sigmatel.com (squirt.sigmatel.com [207.170.89.12]) by hub.freebsd.org (Postfix) with ESMTP id 94E4537B401 for ; Mon, 4 Dec 2000 09:15:26 -0800 (PST) Received: from chaos.sigmatel.com (drift@chaos.sigmatel.com [192.168.7.73]) by mcfeely.sigmatel.com (8.10.2/8.10.2) with ESMTP id eB4HFEu06838 for ; Mon, 4 Dec 2000 11:15:17 -0600 Date: Mon, 4 Dec 2000 11:13:59 -0600 (CST) From: Brandon Williams To: freebsd-questions@freebsd.org Subject: NFS file locking in 4.2-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. 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. 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. $egg->face = 1; -------------------------- Brandon Williams Unix Systems Administrator SigmaTel, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message