From owner-freebsd-current  Fri Oct 24 03:12:34 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id DAA06947
          for current-outgoing; Fri, 24 Oct 1997 03:12:34 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from solist. ([193.219.246.204])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA06941;
          Fri, 24 Oct 1997 03:12:29 -0700 (PDT)
          (envelope-from girgen@partitur.se)
Received: from partitur.se by solist. (SMI-8.6/SMI-SVR4)
	id MAA02559; Fri, 24 Oct 1997 12:10:47 +0200
Message-ID: <34507427.7975BEFD@partitur.se>
Date: Fri, 24 Oct 1997 12:10:47 +0200
From: Palle Girgensohn <girgen@partitur.se>
Organization: Partitur
X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.5.1 sun4u)
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.ORG
CC: dwmalone@maths.tcd.ie, gnat@frii.com, current@FreeBSD.ORG
Subject: Re: -STABLE reboots
References: <199710220037.KAA17789@godzilla.zeta.org.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Hi!

I have a similar problem, that I have seen before, although not this
bad:

I rebooted an nfs server yesterday evening, after a kernel rebuild.
Today, a df on a workstation that had the server mounted prduced an
immediate crash (no kernel panic, really; the screen just went black),
and the system rebooted! I have never seen a FreeBSD machine crash
before, at least from software(?) error! The stable is a few weeks old:
Thu Oct  9 10:45:58 CEST 1997
 
How do I prevent this? It is not the first time nfs gives me problems
when I take down a server. My guess is that I need to uncomment a few
lines in inetd.conf regarding rpc.* so the server can broadcast that it
is going down. Now it's untouched from the release. Am I right?

Regards,
Palle