Xref: utzoo comp.unix.questions:6251 comp.unix.wizards:7370 comp.arch:4080 Path: utzoo!mnetor!uunet!yale!cmcl2!phri!roy From: roy@phri.UUCP (Roy Smith) Newsgroups: comp.unix.questions,comp.unix.wizards,comp.arch Subject: Re: RFS vs. NFS Message-ID: <3215@phri.UUCP> Date: 25 Mar 88 23:31:58 GMT References: <4112@vdsvax.steinmetz.ge.com> <7544@brl-smoke.ARPA> Reply-To: roy@phri.UUCP (Roy Smith) Organization: Public Health Research Inst. (NY, NY) Lines: 17 gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) writes: > >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! 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, you have the option of soft mounting a file system, which lets NFS operations time out. Since this is bad for r/w file system and overloaded-but-not-dead-yet servers, you can also mount file systems hard, but with the "intr" option which never times out on its own, but does allow the process to be killed (I guess it sleeps with a low, but non-negative priority) -- Roy Smith, {allegra,cmcl2,philabs}!phri!roy System Administrator, Public Health Research Institute 455 First Avenue, New York, NY 10016