Xref: utzoo comp.sys.sequent:709 comp.sys.hp:6266 comp.protocols.nfs:1298
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!fletcher
From: fletcher@cs.utexas.edu (Fletcher Mattox)
Newsgroups: comp.sys.sequent,comp.sys.hp,comp.protocols.nfs
Subject: Re: HP <-> Sequent NFS botch
Message-ID: <12773@cs.utexas.edu>
Date: 22 Sep 90 22:05:15 GMT
References: <12609@cs.utexas.edu> <1990Sep18.061958.27946@math-cs.kent.edu> <2844@sequent.cs.qmw.ac.uk>
Followup-To: comp.sys.sequent
Organization: Dept of Computer Sciences, UTexas, Austin
Lines: 12

William Roberts writes:

>Does it only happen with the HP machine as the client, or do you
>get a similar effect when the Sequent is the client and the HP is
>the server?

Actually, it happens only with a Sequent client and HP server 
(I thought my script made that clear--maybe not)..

Turns out to be a problem in the Dynix 3.0.4 NFS client code.
It's fixed in 3.0.14.  If you aren't running that, you should
upgrade your Sequent before going to HPUX 7.0.