Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!mips!apple!well!jef
From: jef@well.UUCP (Jef Poskanzer)
Newsgroups: comp.windows.x
Subject: Re: Remote xterm strategy
Message-ID: <15383@well.UUCP>
Date: 6 Jan 90 07:04:30 GMT
References: <1990Jan5.184224.7960@sdr.slb.com>
Reply-To: Jef Poskanzer <jef@well.sf.ca.us>
Organization: Paratheo-Anametamystikhood Of Eris Esoteric, Ada Lovelace Cabal
Lines: 47

In the referenced message, saito@slb-sdr.UUCP (Naoki Saito) wrote:
}	(2) rsh remote_machine 'xterm -display localhost:0' &

This is the method I used until recently.  See the appended script for
details, including .login reading and DISPLAY setting.

}	(1) xterm -e rlogin remote_machine &

This is the method I use now.

}(2) is slightly lighter(i.e. better), I think.

No, I don't think so.  (2) is cheaper in terms of memory used on the
server machine.  This was a major consideration what I was trying to
bring up X11alpha on a 2 meg MacII.  These days it is not a concern.
Now I worry more about network efficiency, and the rlogin protocol is
quite a bit more efficient than the X protocol.

The only problem is, I haven't figured out a good way to get DISPLAY
set correctly using the rlogin method.
---
Jef

  Jef Poskanzer  jef@well.sf.ca.us  {ucbvax, apple, hplabs}!well!jef
                         For indoor use only.

- - - - - - - - - -

#!/bin/csh -f
#
# rX - remotely execute an X command without leaving cruft behind
#
# Assumes login shell is /bin/csh.
#
# by Jef Poskanzer - version of 07feb89

switch ( $#argv )
case [01]:
	echo "Usage: $0 host X-cmd [args...]"
	breaksw
default:
	set host="$1"
	shift
	xhost "$host"
	rsh "$host" "( source .login ; setenv TERM xterm ; setenv DISPLAY `hostname`:0 ; ( $* & ) ) < /dev/null >& /dev/null" < /dev/null >& /dev/null &
	breaksw
endsw