From owner-freebsd-hackers  Thu Mar 18  8: 7: 2 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from etinc.com (et-gw.etinc.com [207.252.1.2])
	by hub.freebsd.org (Postfix) with ESMTP id 8F45F1508C
	for <hackers@freebsd.org>; Thu, 18 Mar 1999 08:00:01 -0800 (PST)
	(envelope-from dennis@etinc.com)
Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id LAA21997 for <hackers@freebsd.org>; Thu, 18 Mar 1999 11:04:02 -0500 (EST)
Message-Id: <199903181604.LAA21997@etinc.com>
X-Sender: dennis@etinc.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Thu, 18 Mar 1999 10:52:56 -0500
To: hackers@freebsd.org
From: Dennis <dennis@etinc.com>
Subject: NFS - Will it ever be fixed?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


NFS continues, after many many years, to virtually lock up systems
when the server goes away and anything on it is in the path. If you
try to dismount it locks up also.

Is there a way around the 3 hour waiting period (it seems) for the system
to realize that the server is gone?

Dennis


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message