‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, October 29, 2020 7:47 PM, Ulrich Sibiller <uli42@gmx.de> wrote:
On Fri, Oct 30, 2020 at 12:15 AM kht-lists kht-lists@protonmail.ch wrote:
machine with an SSH terminal and examining what is running it appears that the remote SESSION is running, not suspended (which my research lead me to believe should happen.) And I can reconnect to the remote session which is a good thing. Thanks.
x2goagent will always be running for the session, this is the session's X server. "Suspended" means it will use less cpu cycles.
On Linux I can launch many instances of the x2goclient. However, each instance of the x2goclient can only connect to ONE remote machine. I am spoiled from using vinagre to connect to conventional vnc sessions. It presents them in a tabbed interface. Very space efficient and easy to switch between remotes.
Yes, x2goclient should have something like that. Someone should code that...
Uli
Thanks again Uli,
I will have to do some experimenting and monitor CPU usage. Other than the client interface I am pleased with x2go. It was VERY easy to setup and seems very efficient.
I have used vnc4 and Tigervnc going back to probably Red Hat (not enterprise) 8 or 9. I always thought it was cool to be able to connect to a remote PC and do my business without having to interact with the physical console. Sort of like a REAL (mainframe) computer :-) The biggest stumbling block to using these products has been the xstartup script. Some of it I understand and some of it I have no clue. Over many years I have taken a working one, moved it to the next OS version, looked on-line and tweaked it until it worked. I had vnc4 working on Ubuntu Mate 18.04 but it is not available on 20.04. I have used Tight/Tiger on CentOS 6 and 7 but my xstartup would not work on Ubuntu.
Yesterday I found a tutorial on setting up Tightvnc on Ubuntu 20.04. The example used the XFCE desktop. I followed it and it worked! I tried to clone the process onto my Ubuntu Mate 20.04 test machine. No go. I started stripping lines out of the xstartup which I did not understand. I ended up with one new line from the XFCE example and 2 from my old script which worked on 18.04. The vncserver runs and I can connect to it !!! I get a couple of pages of log from the startup - mostly error - but that seems to always happen.
CPU utilization by the Tightvnc server seems to be in the middle. More than x2go but less than x11vnc.
Again my thanks,
Ken in North Carolina, USA