From owner-freebsd-current  Thu Oct 17 12:59:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA25490
          for current-outgoing; Thu, 17 Oct 1996 12:59:23 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA25485;
          Thu, 17 Oct 1996 12:59:19 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA20119; Thu, 17 Oct 1996 13:58:38 -0600 (MDT)
Date: Thu, 17 Oct 1996 13:58:38 -0600 (MDT)
Message-Id: <199610171958.NAA20119@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: dyson@freebsd.org
Cc: current@freebsd.org
Subject: Re: How is the NFS forcible dismount patch running?
In-Reply-To: <199610161412.JAA03363@dyson.iquest.net>
References: <199610161412.JAA03363@dyson.iquest.net>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

John S. Dyson writes:
> Hopefully the AMD (automounter) problems are pretty much gone?

I didn't get time to update my box to -current until this morning, and
with the patch in place here are my results.

Setup:
client : P75/24MB -current as of late last night
options: rw,soft,intr,bg,noauto

server : Ultra Sparc Slolaris 2.5

Test:

client # cd /nfs
client # tar cf - /dev/null . &
client # tar cf /dev/null . &
client # tar: read error at byte 0, reading 1024 bytes, in file tmp/ssh/ssh-1.2.12/servconf.h : Interrupted system call

Even so, it ran to completion after a couple hours. :)

(The exported FS takes up most of a 4GB disk).




Nate