Path: utzoo!attcan!uunet!munnari.oz.au!uhccux!ames!purdue!decwrl!ucbvax!hplabs!otter!hpubrcf!ken
From: ken@hpubrcf.HP.COM (Ken Green)
Newsgroups: comp.windows.x
Subject: Re: Remote xterm strategy
Message-ID: <130001@hpubrcf.HP.COM>
Date: 10 Jan 90 11:31:10 GMT
References: <1990Jan5.184224.7960@sdr.slb.com>
Organization: HP  UK Response Center
Lines: 21

> A very useful program that no one's written is xrlogin (or xtelnet, or
> xsupdup).  This combines xterm and rlogin in one process (it speaks
> rlogin protocol itself), and does not allocate a pty on the local
> machine.  On the other hand, it requires a host to be specified on the
> command line.  Given that a major use of xterm is to rlogin to a remote
> machine, this would seem a very useful program to me...

	I tackled this problem rather differently.... I wrote a simple 
	remsh ( rsh ) type command that doesn't keep daemon processes lying
	around. You then just ask the remote system to throw you back an
	xterm window.

	My workstation currently has 73 windows started by remote users
	and I sure didn't want the overhead of running 73 remshd.

	The other thing I found useful was to take over all the enviroment
	variables. ( Not so usefull between different system types, but a 
	great boon that the DISPLAY variable goes ).


			Ken 'Now I just need more memory' Green