From owner-freebsd-current  Wed Oct 16 07:38:12 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA06017
          for current-outgoing; Wed, 16 Oct 1996 07:38:12 -0700 (PDT)
Received: from dyson.iquest.net ([198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA06009;
          Wed, 16 Oct 1996 07:38:07 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id JAA03426; Wed, 16 Oct 1996 09:38:05 -0500 (EST)
From: John Dyson <dyson@dyson.iquest.net>
Message-Id: <199610161438.JAA03426@dyson.iquest.net>
Subject: Re: How is the NFS forcible dismount patch running?
To: dyson@freebsd.org
Date: Wed, 16 Oct 1996 09:38:05 -0500 (EST)
Cc: current@freebsd.org
In-Reply-To: <199610161412.JAA03363@dyson.iquest.net> from "John S. Dyson" at Oct 16, 96 09:12:24 am
Reply-To: dyson@freebsd.org
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Hopefully the AMD (automounter) problems are pretty much gone?
> 
It was too early for me to be coherent when I asked the question :-).  What
I meant was that last night, I fixed a problem with the rundown of
vnode that manifested itself as a problem with forcible NFS unmounts...

Does NFS look more stable now?  is a better way of asking the question :-).

John