Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ogicse!hakanson
From: hakanson@ogicse.ogc.edu (Marion Hakanson)
Newsgroups: comp.windows.x
Subject: Re: Remote xterm strategy
Message-ID: <6517@ogicse.ogc.edu>
Date: 7 Jan 90 00:49:31 GMT
References: <90Jan6.054031est.2293@neat.cs.toronto.edu>
Reply-To: hakanson@cse.ogi.edu (Marion Hakanson)
Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR
Lines: 13

In article <90Jan6.054031est.2293@neat.cs.toronto.edu> moraes@csri.toronto.edu writes:
>Quick answer -- use (2) preferably with rcmd instead of rsh, and with
>xterm's -ls option for machines on the local network that you trust,
>use (1) for all others.

There's also xrsh, in R4/contrib/clients/xrsh/, which does pretty much
the same thing as rcmd.  A quick scan convinces me that rcmd is
fancier, but xrsh should win a footrace (and start up a lot fewer
processes).  Choose your poison....

-- 
Marion Hakanson         Domain: hakanson@cse.ogi.edu
                        UUCP  : {hp-pcd,tektronix}!ogicse!hakanson