On Fri, Jan 17, 2020 at 4:08 PM Tristan Miller <psychonaut@nothingisreal.com> wrote:
Greetings.
On Fri, 17 Jan 2020 15:46:15 +0100, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 16.01.20 um 15:19 schrieb Tristan Miller:
Maybe he has the same use case as me: at work I often make an X2Go connection from my office computer to my home computer. Sometimes I forget to terminate the connection before I come home from work, so I need to do it using x2goterminate-session on the "remote" server once I get home.
That sounds wrong. You can remote-suspend a session between a client A and a server from another client B you're logged on to, and resume it from there. No need to terminate the session.
Suspending doesn't help when I want to locally run a program on the server (like my mail client or web browser) that permits only one instance at a time, and the X2Go session is already running such an instance. Or is there some way of moving a program from an X2Go session to the local display? (If there is, I expect it's not going to be any easier than manually killing the application, or simply terminating the entire X2Go session, and then restarting the program locally.)
Am I getting something wrong here? You have an X2go session where program X is running and you need to run program X again which is not possible because it is running within the x2go session. So instead of connecting to the session and continuing to use the running instance of program X you kill the whole session and start a new one where you again start programX? Why?
Reconnecting to running sessions is one of the core purposes of X2go (or NX).
Uli