From owner-freebsd-questions Fri Nov 17 07:55:17 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA11937 for questions-outgoing; Fri, 17 Nov 1995 07:55:17 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA11922 for ; Fri, 17 Nov 1995 07:55:07 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id IAA05557; Fri, 17 Nov 1995 08:52:20 -0700 From: Terry Lambert Message-Id: <199511171552.IAA05557@phaeton.artisoft.com> Subject: Re: Poor NFS performance under FreeBSD To: archive@cps.cmich.edu (Mail Archive) Date: Fri, 17 Nov 1995 08:52:20 -0700 (MST) Cc: terry@lambert.org, mikhail@klm.com, freebsd-questions@FreeBSD.org In-Reply-To: from "Mail Archive" at Nov 16, 95 10:27:50 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 972 Sender: owner-questions@FreeBSD.org Precedence: bulk > > The lockd/stad have to do with file locking andwon't affect write > > performance at all (unless you use an unlock as a trigger for client > > cache flushing, and even then your processes would have to know > > about it and cooperate). > > Anyone know the status of lockd/statd :) I would really like to scrap > Solaris x86 for FreeBSD file serving but until I have statd/lockd I am > stuck :( Andrew has a fully functional rpc.statd. Since only he and I have kernels with my Sun-style hostid/proxy fcntl changes integrated, the rpc.lockd is pretty much stubbed. He has promised to send the code he does have to me this weekend. I've been hacking locking code at work and my employer doesn't object, so I'm going to be hacking on the rpc.lockd code to turn the stubs into real calls as time and stub availability permits. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.