From owner-freebsd-current Mon Nov 13 10:28:35 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA16707 for current-outgoing; Mon, 13 Nov 1995 10:28:35 -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 KAA16698 for ; Mon, 13 Nov 1995 10:28:31 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA16943; Mon, 13 Nov 1995 11:23:01 -0700 From: Terry Lambert Message-Id: <199511131823.LAA16943@phaeton.artisoft.com> Subject: Re: ISP state their FreeBSD concerns To: karl@mcs.com (Karl Denninger, MCSNet) Date: Mon, 13 Nov 1995 11:23:01 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: from "Karl Denninger, MCSNet" at Nov 12, 95 09:59:26 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 940 Sender: owner-current@FreeBSD.org Precedence: bulk > The only other issue we have here is the nasty NFS-write problem that makes > shared access to remote resources tricky at best. If *THAT* was fixed we > would be running FreeBSD exclusively here. Is this the "write with no permission truncate" or what? What is this NFS write problem? > I've been using FreeBSD exclusively for news service for quite a while > (some clients use NFS, others NNTP to read) and its been fine. What we > have a problem with is using it for our web server and general user system > farm; the small NFS writes that the httpds do to the log disks cause system > lockups and hundreds of processes in a hung state. The problem is understood, > but there is no immediate path to a fix from what I've been told. Who understands this problem, so I can talk to them? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.