Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!dogie.macc.wisc.edu!uwvax!rutgers!aramis.rutgers.edu!geneva.rutgers.edu!hedrick From: hedrick@geneva.rutgers.edu (Charles Hedrick) Newsgroups: comp.protocols.nfs Subject: Re: hard vs. soft mounts on Suns and Pyramids Message-ID: Date: 2 May 89 19:58:33 GMT References: <15766@bellcore.bellcore.com> <840@mtxinu.UUCP> <2626@elxsi.UUCP> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 21 I have yet to see a case on the Sun where you couldn't ^C out of a hung NFS connection when intr is set. However it only checks for interrupts at one point in the code. Depending upon how timeouts are set, it can take a couple of minutes to get out. I agree that this is very frustrating. My three big gripe for NFS are: - ^C should happen immediately - df should not hang if one of the servers is hung. It should simply print "server not responding" on that line and go on to the next. (Pyramid attempted to make this work, by allowing a program to specify that disk access should be treated as soft just for this program, even if the disk is mounted hard.) - pwd, getcwd, etc., should be coded so that they don't hang unless your current directory is actually on the hung server NFS is very useful, but our users have gotten to hate it. (It doesn't help that SunOS 4.0 has several bugs that cause NFS to hang. They're slowing being fixed, but our users are never going to forgive me for putting them through this. Of course *I'm* to blame personally for all Sun bugs.)