Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tiamat!bahamut!jim
From: jim@bahamut.fsc.com (James O'Connor)
Newsgroups: comp.windows.x
Subject: Re: Remote xterm strategy
Keywords: rlogin, rsh, xterm
Message-ID: <264@bahamut.fsc.com>
Date: 10 Jan 90 02:25:47 GMT
References: <1990Jan5.184224.7960@sdr.slb.com>
Organization: Filtration Sciences - Chattanooga,TN
Lines: 28

In article <1990Jan5.184224.7960@sdr.slb.com>, saito@sdr.slb.com (Naoki Saito) writes:
> 	(2) rsh remote_machine 'xterm -display localhost:0' &
> 		This invokes rsh command.  A disadvantage is that .login is not
> 		executed on the remote_machine.
> 
> Except the disadvantage of (2), (2) is slightly lighter(i.e. better), I think.
> Could you give me some comments?  Is (2) really better than (1)?  Is there any
> way to solve the disadvantage of (2)?

Since a user who wanted to use (2) would probably have a home directory on the
remote machine, that user could create a shell script in that directory 
containing:

. /u/whoever/.profile
xterm &

and then run it with "rsh remote_machine 'DISLPAY=localhost:0 shell_script'"
This should add a advantage in that the rsh will not get left in the background
like it would under (2).

Also, HP's hpterm has an option which causes hpterm to start the shell with a
"-" prepended so that it will read the "login" files on it's own.  I
remember checking the man page for xterm, but I don't remember if it has this
option as well.
------------- 
James B. O'Connor			Work:	jim@tiamat.fsc.com
Data Processing Manager  		Play:   jim@bahamut.fsc.com
Ahlstrom Filtration, Inc.		UUCP:	uunet!tiamat!jim