From owner-freebsd-current Thu Nov 12 16:47:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22746 for freebsd-current-outgoing; Thu, 12 Nov 1998 16:47:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22734 for ; Thu, 12 Nov 1998 16:47:03 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id TAA101462 for ; Thu, 12 Nov 1998 19:47:39 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199811122213.QAA22227@mnw.eas.slu.edu> Date: Thu, 12 Nov 1998 19:46:48 -0500 To: current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Is it soup yet? FreeBSD NFS Server Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:13 PM -0600 11/12/98, Eric Haug wrote: > I have been using FreeBSD 3.0-CURRENT Mon Nov 2 > as a NFS server to our network of Sparcs. Since the > patch for freeing a null pointer was applied it has > not crashed. Our CS dept has a number of freebsd machines which are NFS servers for some sparc, irix, and freebsd boxes. I think the servers are all freebsd 2.2.6 or later (but not 3.). If they're doing version 2 NFS, then everything is quite fine. If they're setup to do version 3 NFS, then access from the sparcs (or irix, I forget) would regularly cause the freebsd servers to crash. I don't know if the version 3 NFS problems have been addressed in 3.0-current. Seems to me that someone (Terry Lambert?) had some patches which were an initial stab of fixing these problems, but I might be getting mixed up on that. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message