Xref: utzoo comp.unix.questions:6260 comp.unix.wizards:7378 comp.arch:4089
Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!ncar!ames!pasteur!ucbvax!bloom-beacon!bu-cs!bzs
From: bzs@bu-cs.BU.EDU (Barry Shein)
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.arch
Subject: Re: RFS vs. NFS
Message-ID: <20961@bu-cs.BU.EDU>
Date: 26 Mar 88 07:23:26 GMT
References: <326@ivory.SanDiego.NCR.COM> <7765@apple.Apple.Com> <7533@brl-smoke.ARPA> <4112@vdsvax.steinmetz.ge.com> <7544@brl-smoke.ARPA>
Organization: Boston U. Comp. Sci.
Lines: 17
In-reply-to: gwyn@brl-smoke.ARPA's message of 25 Mar 88 09:37:56 GMT



Doug Gwyn replying to someone
>>If an NFS server reboots, the clients just waits and then continue on.
>
>Typically an attempt to access a file on a down link causes the process
>to BLOCK at UNINTERRUPTIBLE priority!  I have been quite pissed off at
>this, on more than one occasion.  It's great fun to type "df" and then
>find that you're never going to get any farther...

No doubt I won't be the only person to point out that this is all now
settable in fstab, you can distinguish hard (hang on failure), soft
(error on failure) and intr (allow interrupts), it's become just a
system admin issue (some of those options were not available w/
previous releases so you used to be right, like I said, let's get it
fixed and get on with other things.)

	-Barry Shein, Boston University