Path: utzoo!utgpu!watmath!clyde!att!pacbell!ames!mailrus!purdue!decwrl!labrea!csli!gandalf
From: gandalf@csli.STANFORD.EDU (Juergen Wagner)
Newsgroups: comp.windows.x
Subject: Re: Starting remote xterms
Message-ID: <6621@csli.STANFORD.EDU>
Date: 1 Dec 88 04:27:59 GMT
References: <5345@polya.Stanford.EDU> <4292@umd5.umd.edu>
Reply-To: wagner@arisia.xerox.com (Juergen Wagner)
Organization: Center for the Study of Language and Information, Stanford U.
Lines: 26

In article <4292@umd5.umd.edu> jonnyg@umd5.umd.edu (Jon Greenblatt) writes:
>In article <5345@polya.Stanford.EDU> weening@Gang-of-Four.Stanford.EDU
>(Joe Weening) writes:
>>    "rsh remotehost -n 'exec /usr/bin/X11/xterm >& /dev/null' &"
>
>	This is a very inefficient way of doing things. The X Window buffers
>ar far more numerous than the equivalent rsh buffers as far as I know.
>Try the following:
>
>	"xterm -e rlogin remotehost"
>...

That's not the point. The two rsh processes will go away as soon as the remote
job is done (i.e. as soon as the xterm is forked). There won't be any rsh's
sitting around and idling. The xterm will just open a connection to the X
server, independently of the rsh line.

Now here a suggestion: I have no idea what is broken in rsh/xterm/..., and
what changed form R2 to R3. How about
	rsh HOST -n "xterm ${DISPLAY} >& /dev/null &"
and dropping the exec. I think the DISPLAY is necessary. It works for me.

Good luck,
-- 
Juergen Wagner		   			gandalf@csli.stanford.edu
						 wagner@arisia.xerox.com