🚀 go-pugleaf

In article <12609@cs.utexas.edu>, fletcher@cs.utexas.edu (Fletcher
Mattox) writes:
> Anybody seen this type of NFS authentication botch?
> 
> The server, taklamakan, is an HP 9000/370 running HPUX 7.0.
> The client, cs.utexas.edu, is a Sequent Balance 21000 running Dynix 3.0.4.
> 
> What's weird about this is:
> 
> 1.  Once the client is allowed to create the file, presumably
>     by using group privileges, it gets the uid right. 
>     Yet the client still cannot, for example, chmod the file
>     because it thinks the owner is wrong.
> 
> 2.  It only happens between the HP and the Balance; our Symmetry
>     client running 3.0.12 works fine (as do all of our Suns).  There is
>     *very* little difference in the NFS client code between Dynix 3.0.4
>     and 3.0.12.
> 
> 3.  This particular NFS problem doesn't happen with an HPUX 6.5 server.  
>     It only surfaced after we upgraded to 7.0.
> ...

We have a similar problem here involving HP9000's and a Sequent B21000.
When using NFS, data seems to have a very difficult time flowing from
the HP's to the Sequent. NFS writes to the Sequent seem to happen in
small bursts with long pauses in between. NFS reads on the Sequent
from the HP's is similar. There is no problem with any other combination
of Suns, HP's, VAXen, or Encore but a Tektronix workstation was behaving
the same way before it died. :-(

---------------------------------------------------------------------
Jeff Bailey (JRB71) (System Administrator)      <bailey@mcs.kent.edu>
Department of Mathematics and Computer Science
Kent State University
Kent - OH 44242