Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!tut!kannel!Kimmo.Suominen From: Kimmo.Suominen@lut.fi (Kimmo Suominen) Newsgroups: comp.sys.hp Subject: Re: /etc/umount under HP-UX 7.0 on 9k/835 Message-ID: Date: 20 Aug 90 03:15:31 GMT References: <1865@dutrun.UUCP> Sender: kim@kannel.lut.fi Organization: Lappeenranta University of Technology, Finland Lines: 25 In-reply-to: tncsatr@dutrun.UUCP's message of 16 Aug 90 14:00:20 GMT Disclaimer: These are my opinions unless otherwise stated >>>>> On 16 Aug 90 14:00:20 GMT, tncsatr@dutrun.UUCP (Arthur van der Harg) said: Arthur> If I understand the problem well, the solution might be to specify Arthur> 'soft' mounting when you mount the system. I gathered that in those Arthur> cases your own machine wqould not be dependent on the (mal-)functioning Arthur> of the 'home' machine of the file system. I expect (disclaimer: I Arthur> am not completely sure) that in this case you can umount the system Arthur> without waiting for a confirmation from the other machine. I think that Arthur> the confirmation is the problem when the other machine goes down. Sorry, you CAN'T umount even soft mounted NFS partitions. But they won't cause you as much trouble as hard mounted ones, when a server goes down. On the other hand you might have trouble in e.g. getting your programs compiled, because on soft mounted links you get NFS timeouts instead of trying until succesful. Deciding between soft and hard links has many points to consider. On a reliable network it is best to have hard links, but if the links break down often, soft links make your life a lot easier. NOTE: The manual tells to always use hard links on read/write partitions. I haven't had problems, though, even if I run them soft mounted. -- Kim --- "That's what I think."