From owner-freebsd-questions Wed Mar 6 08:59:18 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA04522 for questions-outgoing; Wed, 6 Mar 1996 08:59:18 -0800 (PST) Received: from tomcat1.tbe.com (tomcat1.tbe.com [140.165.31.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA04511 for ; Wed, 6 Mar 1996 08:59:15 -0800 (PST) Received: from [140.165.210.81] by tomcat1.tbe.com via SMTP (940816.SGI.8.6.9/940406.SGI.AUTO) for id KAA10912; Wed, 6 Mar 1996 10:56:26 -0600 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 6 Mar 1996 10:59:12 -0600 To: questions@freebsd.org From: dkelly@tomcat1.tbe.com (David Kelly) Subject: When an NFS server croaks... amd? Sender: owner-questions@freebsd.org Precedence: bulk 140.165.31.92:/disk9/dkelly /disk9 nfs rw,soft,intr,bg 0 0 Am using the above line in /etc/fstab to mount an NFS filesystem. At the moment the remote system has lost its mind. What is the best way to make my FreeBSD system forget about this mount? "umount -f /disk9" blocks until something times out. I could comment it out of /etc/fstab and reboot but that's not sporting. What can I do better to prevent this from happening in the future? Amd(8) shows promise but having amd(8) fake an NFS mount for an NFS mount seems convoluted. Is this the right path to take? -- David Kelly N4HHE, dkelly@tomcat1.tbe.com (wk), dkelly@hiwaay.net (hm) ====================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.