From owner-freebsd-bugs  Wed Oct  1 08:30:04 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id IAA19973
          for bugs-outgoing; Wed, 1 Oct 1997 08:30:04 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id IAA19953;
          Wed, 1 Oct 1997 08:30:02 -0700 (PDT)
Date: Wed, 1 Oct 1997 08:30:02 -0700 (PDT)
Message-Id: <199710011530.IAA19953@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: j@uriah.heep.sax.de (J Wunsch)
Subject: Re: kern/4666: umount -f doesn't seem to work
Reply-To: j@uriah.heep.sax.de (J Wunsch)
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/4666; it has been noted by GNATS.

From: j@uriah.heep.sax.de (J Wunsch)
To: muir@idiom.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/4666: umount -f doesn't seem to work
Date: Wed, 1 Oct 1997 17:10:51 +0200

 As muir@idiom.com wrote:
 
 >     tmp:/	 /net/tmp  nfs	ro,intr,bg,tcp,nfsv2,resvport,nosuid 0 0
 >     tmp:/usr /net/tmp/usr  nfs	ro,intr,bg,tcp,nfsv2,resvport,nosuid 0 0
 > 
 > >Description:
 > 
 > 	 # umount -f -h tmp
 > 	 nfs server tmp:/: not responding
 
 This is what one would expect how umount -f is working, but not what
 is described for umount -f: forcibly unmounting is currently only
 defined as ``don't care about resources that are locally still in use,
 but revoke them''.
 
 Anyway, i think this is already in Doug Rabson's queue of ``nice to
 have'' things.  If i'm not totally mistaken, there might already be
 another open PR for it.  Did you check before filing?
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)