From owner-freebsd-current  Mon Jun  8 22:28:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA04133
          for freebsd-current-outgoing; Mon, 8 Jun 1998 22:28:54 -0700 (PDT)
          (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 WAA04127
          for <current@freebsd.org>; Mon, 8 Jun 1998 22:28:52 -0700 (PDT)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.8/8.8.5) id AAA02019
	for current@freebsd.org; Tue, 9 Jun 1998 00:28:50 -0500 (CDT)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199806090528.AAA02019@home.dragondata.com>
Subject: NFS Discovery Part 2
To: current@FreeBSD.ORG
Date: Tue, 9 Jun 1998 00:28:49 -0500 (CDT)
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


Ok... A few more things...

1) 'killall -HUP mountd' still causes -STABLE servers to panic: vfs_unlock:
not locked  I filled out a PR a while back, but can't find it now...

2) Someone asked what processes would get 'hung' in, when the nfs server
goes down... 'nfsrcv'... Their priority also goes to -10(or so) when they're
stuck like this. kill -9 doesn't kill them.


Kevin

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