Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!menudo.uh.edu!buster!chemsh!chemsh.uucp!dla
From: dla@chemsh.uucp (Doug Acker)
Newsgroups: comp.sys.apollo
Subject: Re: NFS 2.2 bombs
Message-ID: <1991Jun17.190849.3182@chemsh.uucp>
Date: 17 Jun 91 19:08:49 GMT
References: <1991Jun11.233532.1920@chemsh.uucp> <1991Jun12.175533.2004@chemsh.uucp> <2694@m1.cs.man.ac.uk>
Sender: root@chemsh.uucp
Reply-To: dla@chemsh.uucp (Doug Acker)
Organization: ChemShare
Lines: 30

In article <2694@m1.cs.man.ac.uk>, dente@els.ee.man.ac.uk (Colin Dente) writes:
|> In article <1991Jun12.175533.2004@chemsh.uucp> dla@chemsh.uucp (Doug Acker) writes:
|> >In article <1991Jun11.233532.1920@chemsh.uucp>, dla@chemsh.uucp (Doug Acker) writes:
|> >|> I'm another person who found that NFS 2.2 bombs on a 425s ...
|> >|> Has anyone found a fix or has HP/Apollo Acknowledged the problem?
|> >
|> >Talking to Apollo, this problem is with csh ... if you run csh scripts over
|> >a mount point, it gets hosed and dies.  They are working on a patch.  Also
|> >with NFS2.3, it will support automounting ....
|> 
|> Does this mean that if I avoid csh scripts, then NFS2.2 should be
|> usable? (I don't mean good - just *usable* ;-/) - I was just getting
|> excited about the prospect of a usable version of NFS when all these
|> horror stories started appearing... might I actually dare to use
|> NFS2.2?
|> 
|> Colin
|> 

I think that would be a correct statement.

-- 


Douglas L. Acker

ChemShare Corporation
DesignMaster Division

dla@chemsh.UUCP       713-267-5602