From owner-freebsd-current Tue Mar 30 19:13: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 31BFD15503 for ; Tue, 30 Mar 1999 19:13:04 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from waltz.rahul.net by bolero-x.rahul.net with SMTP id AA10821 (5.67b8/IDA-1.5 for ); Tue, 30 Mar 1999 19:12:30 -0800 From: Rahul Dhesi Received: by waltz.rahul.net (5.67b8/jive-a2i-1.0) id AA09775; Tue, 30 Mar 1999 19:11:06 -0800 Date: Tue, 30 Mar 1999 19:11:06 -0800 Message-Id: <199903310311.AA09775@waltz.rahul.net> To: freebsd-current@freebsd.org Subject: Re: nfs problems References: X-Newsreader: NN version 6.5.1 (NOV) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: >This is freebsd following the NFS spec, please read the mount_nfs >man page for the workaround (hint: intr). In my experience the 'intr' filesystem mount option does not always work. As an example, I am often unable to abort from a hung 'df' when a remote NFS server is down. (Even if my current directory is not NFS-mounted.) This might be a problem specific to 'df', though. Ideally 'df' should check to make sure a remote NFS server is responding (via the NFS null procedure) before trying to get any filesystem info for that filesystem. -- Rahul Dhesi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message