From owner-freebsd-questions Thu Nov 16 19:28:42 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA07566 for questions-outgoing; Thu, 16 Nov 1995 19:28:42 -0800 Received: from cps201.cps.cmich.edu (cps201.cps.cmich.edu [141.209.20.201]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA07527 for ; Thu, 16 Nov 1995 19:28:22 -0800 Received: from cps201 (cps201.cps.cmich.edu [141.209.20.201]) by cps201.cps.cmich.edu (8.6.12/8.6.12) with SMTP id WAA07448; Thu, 16 Nov 1995 22:27:50 -0500 Date: Thu, 16 Nov 1995 22:27:50 -0500 (EST) From: Mail Archive X-Sender: archive@cps201 To: Terry Lambert cc: Mikhail Kuperblum , freebsd-questions@FreeBSD.org Subject: Re: Poor NFS performance under FreeBSD In-Reply-To: <199511170159.SAA04239@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org Precedence: bulk On Thu, 16 Nov 1995, Terry Lambert wrote: > 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 :( Matthew S. Bailey