Xref: utzoo comp.unix.questions:6266 comp.unix.wizards:7387 comp.arch:4093
Path: utzoo!mnetor!uunet!husc6!yale!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.arch
Subject: Re: RFS vs. NFS
Message-ID: <7555@brl-smoke.ARPA>
Date: 26 Mar 88 14:59:46 GMT
References: <4112@vdsvax.steinmetz.ge.com> <7544@brl-smoke.ARPA> <3215@phri.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <3215@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
>gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>> Typically an attempt to access a file on a down link causes the process
>> to BLOCK at UNINTERRUPTIBLE priority!
>	You must be using an oldish version of NFS; I think this is the way
>it worked in SunOS-3.0, with 3.2 and later, ...

Sounds like Sun is working on the problems, which is good.
By the way, my hung "df" occurred on a Gould UTX-32 system,
not on a Sun, although the down fileserver may have been a
Sun (with the system wedging every time I touched the
filesystem, it was hard to tell).  Perhaps one or both of
the workarounds you mentioned was available and the system
administrator had made a mistake.  (Not my system!)