Run GUI software over SSH for a long run?

Question

linux

There is a server (Ubuntu 11.04) on which there are virtual machines. I want to run the software on one of the virtual machines for a long time. I did this:
via SSH (with X forwarding) I connected to the server, launched the virtual machine and ran the software there (also graphical). But for this whole thing to work, SSH must be running all the time. Otherwise, all spawned processes via SSH are killed when the connection is lost. How can I avoid this? As far as I've heard, SSH+screen for graphics doesn't work.
Do not install VNC on the server, because when restarting and before logging into the system, the server will not work. And I don’t really want the curious to see what’s happening there on the server screen.
They suggested that I install nomachine . I want to know what other options are there?

Answer 1

Do not install VNC on the server, because when restarting and before logging into the system, the server will not work. And I don’t really want the curious to see what’s happening there on the server screen.

Eeemmmm… Install some tightvnc-server, run it, it creates a separate X display, which is visible only to those connected via VNC. Accordingly, you make it so that it listens only to the localhost, and connect through an SSH tunnel, so that the traffic will be encrypted. I do not understand why VNC is not satisfied.

Answer 2

ssh -X [email protected]
screen -S test
DISPLAY=:0 chromium-browser

The latter is already launched in the screen session. The environment variable says to use the first (or rather zero) display, which is the host's native display by default. I just tried it on two computers and it worked. Maybe you can do it too. Good luck.

Answer 3

To unbind from the console, IMHO, it is most convenient to use screen.
And to output Xs “to nowhere” there is such a thing as en.wikipedia.org/wiki/Xvfb .
Those. "Xserver with Virtual FrameBuffer". Then no one will see your display, including you (but you can take screenshots!). Sometimes this is convenient if your count. the application only needs to be launched, but not run in it, and for some reason, Xs cannot be launched on the “client” side.

Answer 4

+1 for vncserver. It will not display an image on the monitor, and you can put a password on it.

Answer 5

> Otherwise, all spawned processes via SSH are killed when the connection is lost
Unlink from the console, and will not be killed:
$ (/usr/bin/myprogram &)