Xref: utzoo comp.graphics:18003 comp.sys.sgi:10082 comp.graphics.visualization:569
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!sgi!vjs@rhyolite.wpd.sgi.com
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Newsgroups: comp.graphics,comp.sys.sgi,comp.graphics.visualization
Subject: Re: Distributed GL graphics via high speed networks...
Message-ID: <103787@sgi.sgi.com>
Date: 14 May 91 17:20:48 GMT
References: <1991May13.191050.21842@eagle.lerc.nasa.gov> <103732@sgi.sgi.com>
Sender: guest@sgi.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 13


The easiest way to debug a .rhosts problem on an IRIS is to use the command
`rsh host -l guest env` and then to examine the values of REMOTEHOST and
REMOTEUSER to see that they match the target .rhosts file.  (Of course,
if there is no open account such as guest, you have to `rlogin host`, type
a password, and then use `env`, `printenv`, `echo $REMOTEHOST`, or whatever.)

As Gary wrote, many things can cause the remote machine to use different
values for either of those variables.  Their values are obtained
from the rsh protocol and getpeername(2) and gethostbyaddr(3).


Vernon Schryver,   vjs@sgi.com