From owner-freebsd-hackers Sun Nov 28 23:17:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from 24-25-220-29.san.rr.com (24-25-220-29.san.rr.com [24.25.220.29]) by hub.freebsd.org (Postfix) with ESMTP id C4CCF15343 for ; Sun, 28 Nov 1999 23:17:18 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by 24-25-220-29.san.rr.com (8.9.3/8.8.8) with ESMTP id XAA23882; Sun, 28 Nov 1999 23:16:54 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38422866.6779B268@gorean.org> Date: Sun, 28 Nov 1999 23:16:54 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > On Mon, 22 Nov 1999, David E. Cross wrote: > > > Ok... I have *had* it with the meta, but not really, lockd. Are there any > > kernel issues with correctly implimenting rpc.lockd? I can't help with the code, but put me down as both very interested, and willing to help test. We have a mixed sun, netapp and freebsd nfs environment, and I have some freebsd machines that I can sacrifice to the cause. We are pretty desperate for working NFS file locking at work as well. FWIW, we tried the linux version of lockd on linux and not only did it suck potatoes, it was frequently the cause of that server crashing. I would stay completely away from it. Thanks, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message