From owner-freebsd-current Thu Mar 5 20:30:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22199 for freebsd-current-outgoing; Thu, 5 Mar 1998 20:30:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22143; Thu, 5 Mar 1998 20:29:51 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id WAA22909; Thu, 5 Mar 1998 22:29:28 -0600 (CST) From: Kevin Day Message-Id: <199803060429.WAA22909@home.dragondata.com> Subject: Re: Donations. In-Reply-To: <19980305215754.02721@mcs.net> from Karl Denninger at "Mar 5, 98 09:57:54 pm" To: karl@mcs.net (Karl Denninger) Date: Thu, 5 Mar 1998 22:29:10 -0600 (CST) Cc: dyson@FreeBSD.ORG, shimon@simon-shapiro.org, current@FreeBSD.ORG, jak@cetlink.net, karpen@ocean.campus.luth.se X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know if there has been any recent breakage.... does anyone else have > any serious (ie: heavy-duty) experience in this area that can speak to > whether the -CURRENT tree, as it exists now, is ok in the NFS server area? I've played with it a bit. nfsd under 2.2.5 is stable as a rock. nfsd under -current croaks under heavy load. Trying to backup my -current server over nfs to a slow tape drive can kill it, easily. Usually it's the 'console is still responsive, but all processes are hung.' situation. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message