Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!uwm.edu!cs.utexas.edu!swrinde!hookup!news.kei.com!eff!news.umbc.edu!haven.umd.edu!purdue!mozo.cc.purdue.edu!bj From: bj@ben.com (Ben Jackson) Newsgroups: comp.os.386bsd.questions Subject: BSD box NFS mounting from BSD/DOS box, DOS no habla NFS... Date: 24 Jan 1995 15:31:31 GMT Organization: Top of the Hill at Purdue, West Lafayette, Indiana Lines: 20 Sender: bj@cc.purdue.edu Message-ID: <3g36gj$lhv@mozo.cc.purdue.edu> NNTP-Posting-Host: elbow.cc.purdue.edu Summary: how do I make BSD fail the mount? My machine crossmounts home filesystems with my roommate's (via amd). This is great when both machines are running BSD. When he boots DOS while I have his home directory mounted (all to common since he has usually just logged out of my machine) I end up having a lot of problems with processes (eg find) hanging when they reach /u2. This seems to be due to the fact that under DOS his machine is still on the net, thus behaving as a "bogged down" NFS server that my machine expects will eventually respond (which it does, hours later, when it is running BSD again...). The only solution I've come up with is installing a script on his end to use `amq -h myname -f -u /.hisname/u2' to try to unmount just before going down. This is only a "suggestion" to amd, though. I'd prefer a way to help my NFS client distinguish between "slow NFS response" and "no possible NFS response". Thanks for any suggestions! -- Ben Jackson, bj@cc.purdue.edu