Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #222040 > unrolled thread

Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm

Back to article view | Back to linux.debian.user

Contents

  Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm "Steve Keller" <keller.steve@gmx.de> - 2020-04-28 18:10 +0200
    Re: Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm Greg Wooledge <wooledg@eeg.ccf.org> - 2020-04-28 18:10 +0200
      Re: Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm "Thomas Schmitt" <scdbackup@gmx.net> - 2020-04-28 19:10 +0200
        Re: Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm David Wright <deblis@lionunicorn.co.uk> - 2020-04-28 20:20 +0200
    Re: Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm Dan Purgert <dan@djph.net> - 2020-04-28 19:50 +0200
      Re: Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm David Wright <deblis@lionunicorn.co.uk> - 2020-04-28 20:20 +0200
    Re: Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm "Russell L. Harris" <russell@rlharris.org> - 2020-04-28 21:10 +0200
      Re: Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm l0f4r0@tuta.io - 2020-04-28 21:40 +0200
    Re: Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm Bob McGowan <ramjr0915@gmail.com> - 2020-04-28 22:50 +0200

#222040 — Remote terminal: xterm -e ssh <host> vs. ssh <host> xterm

What are best practices to create a remote terminal?  I see to ways:
Create a local terminal emulator and run ssh to the remote host in
that or call ssh to run the terminal emulator on the remote host,
i.e.

    xterm -e ssh -X <host>      or      ssh -X <host> xterm -ls

What are pros and cons?  I see one: The latter will produce more
overhead as it runs the X11 protocol through the ssh tunnel.

Steve

[toc] | [next] | [standalone]

#222041

On Tue, Apr 28, 2020 at 05:46:33PM +0200, Steve Keller wrote:
>     xterm -e ssh -X <host>      or      ssh -X <host> xterm -ls
> 
> What are pros and cons?  I see one: The latter will produce more
> overhead as it runs the X11 protocol through the ssh tunnel.

I would absolutely prefer the first one, unless you have a specific
reason to use the latter (e.g. you're debugging the xterm program on a
remote system, or you're stuck on a thin client, or Windows platform,
that doesn't have a real terminal emulator installed).

[toc] | [prev] | [next] | [standalone]

#222047

Hi,

Steve Keller wrote:
> >     xterm -e ssh -X <host>      or      ssh -X <host> xterm -ls

Greg Wooledge wrote:
> I would absolutely prefer the first one, unless you have a specific
> reason to use the latter

I agree. But why the -X in the first one ?
Is there more desired than a shell session ?


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#222049

On Tue 28 Apr 2020 at 19:09:48 (+0200), Thomas Schmitt wrote:
> Steve Keller wrote:
> > >     xterm -e ssh -X <host>      or      ssh -X <host> xterm -ls
> 
> Greg Wooledge wrote:
> > I would absolutely prefer the first one, unless you have a specific
> > reason to use the latter
> 
> I agree. But why the -X in the first one ?
> Is there more desired than a shell session ?

I presume the OP wants to be able to run GUIs as well as CLI programs.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#222048

[Multipart message — attachments visible in raw view] — view raw

On Apr 28, 2020, Steve Keller wrote:
> What are best practices to create a remote terminal?  I see to ways:
> Create a local terminal emulator and run ssh to the remote host in
> that or call ssh to run the terminal emulator on the remote host,
> i.e.
> 
>     xterm -e ssh -X <host>      or      ssh -X <host> xterm -ls
> 
> What are pros and cons?  I see one: The latter will produce more
> overhead as it runs the X11 protocol through the ssh tunnel.

I must be missing something key - what's wrong with "ssh user@host" ?

-- 
|_|O|_| Github: https://github.com/dpurgert
|_|_|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860
|O|O|O| Former PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

[toc] | [prev] | [next] | [standalone]

#222051

On Tue 28 Apr 2020 at 13:43:16 (-0400), Dan Purgert wrote:
> On Apr 28, 2020, Steve Keller wrote:
> > What are best practices to create a remote terminal?  I see to ways:
> > Create a local terminal emulator and run ssh to the remote host in
> > that or call ssh to run the terminal emulator on the remote host,
> > i.e.
> > 
> >     xterm -e ssh -X <host>      or      ssh -X <host> xterm -ls
> > 
> > What are pros and cons?  I see one: The latter will produce more
> > overhead as it runs the X11 protocol through the ssh tunnel.
> 
> I must be missing something key - what's wrong with "ssh user@host" ?

I presume the OP is setting up a menu item. You and I are probably
typing into an xterm (or similar) already).

Also I presume that the OP wants the same username at host.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#222054

On Tue, Apr 28, 2020 at 05:46:33PM +0200, Steve Keller wrote:
>What are best practices to create a remote terminal?  I see two ways:

Do not overlook the marvelous package "screen".

[toc] | [prev] | [next] | [standalone]

#222056

Hi,

28 avr. 2020 à 21:04 de russell@rlharris.org:

> On Tue, Apr 28, 2020 at 05:46:33PM +0200, Steve Keller wrote:
>
>> What are best practices to create a remote terminal?  I see two ways:
>>
> Do not overlook the marvelous package "screen".
>
Or even better: tmux :)

Best regards,
l0f4r0

[toc] | [prev] | [next] | [standalone]

#222059

[Multipart message — attachments visible in raw view] — view raw

On 4/28/20 8:46 AM, Steve Keller wrote:
> What are best practices to create a remote terminal?  I see to ways:
> Create a local terminal emulator and run ssh to the remote host in
> that or call ssh to run the terminal emulator on the remote host,
> i.e.
>
>      xterm -e ssh -X <host>      or      ssh -X <host> xterm -ls
>
> What are pros and cons?  I see one: The latter will produce more
> overhead as it runs the X11 protocol through the ssh tunnel.
>
> Steve

I have read several of the responses to this and I think it would help 
to clarify exactly what is happening in each of the two cases.

This is a bit long, my apologies, but to decide which is best, we need 
to know what is happening at all levels.

First, in both cases, you are running some sort of X based environment 
on your local machine.

Case one:  you run an xterm locally which uses your local environment to 
open a window in which an ssh is run on your local machine to open a 
connection to the remote host.  The sshd on the remote executes some 
remote application, in this case a login shell, to communicate with 
you.  You used the -X option to ssh so you could run an X client on the 
remote and it would display on your local host.

Case two:  you run ssh in your local terminal emulator, which could be 
any X terminal emulator (xterm, gnome-terminal, etc). You use the -X 
option to allow the X protocol to communicate from the remote to the 
local, and you run an xterm on the remote, which then displays on your 
local system.  This is all handled by the same sshd that ran a shell, 
above.  You used the -ls option for the remote xterm, which causes it 
run a login shell.  If you should need to run a remote graphical program 
within the remote xterm, it would also open a window on your local system.

The only real difference is, as you noted, the remote xterm overhead.

Since you used the -X option of ssh, I presume you intend to run some 
other graphical application on the remote, so not having a remote xterm 
could reduce overhead from two remote graphical applications.

However, there is no reason whatsoever to run a local xterm from within 
a local terminal emulator, just run the ssh directly:

ssh -X <host>

Or, if you do in fact want to run some remote graphical application:

ssh - x <host> <remote_application>

Unless there is some specific feature of the xterm that you need, that 
other emulators do not supply?

Bob

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web