From owner-freebsd-current  Fri May 12 23:42:25 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id XAA04077
          for current-outgoing; Fri, 12 May 1995 23:42:25 -0700
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA04054
          for <current@freebsd.org>; Fri, 12 May 1995 23:41:58 -0700
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD4.4)
	id QAA02566 for current@freebsd.org; Sat, 13 May 1995 16:41:14 +1000
From: michael butler <imb@asstdc.scgt.oz.au>
Message-Id: <199505130641.QAA02566@asstdc.scgt.oz.au>
Subject: kernel panic w/NFS
To: current@FreeBSD.org
Date: Sat, 13 May 1995 16:41:12 +1000 (EST)
Reply-To: imb@scgt.oz.au
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 465       
Sender: current-owner@FreeBSD.org
Precedence: bulk

Whilst copying some files between machines over NFS, I accidentally managed
to reboot the server of the pair .. the client then suffered a kernel panic
as a direct result. Is it possible to prevent the client from doing this
when the server "goes away" ?

Whilst it doesn't worry me for local connections, it is conceivable that a
link over an ISDN link might also exhibit this behaviour if it goes down at
an inappropriate time (as they usually do :-(),

	michael