On 03.03.2015 03:36 PM, Michael DePaulo wrote:
I feel awkward asking these since I am a developer.
- What are the differences between a session that is "suspend" and a session that is "running" but disconnected?
A suspended session has been gracefully suspended within the client.
A running session could either be an active one currently used, or one that is still waiting for a timeout of the client crashed or the connection was dropped prematurely for any reason. Running sessions should switch into suspended state after a (rather long?) timeout.
You cannot attach to running sessions, but you can forcefully suspend a running session from the client and then attach to it.
- With X2Go Client for Windows at least, sometimes I will connect to an X2go Server and I will see 1 running or suspended session listed in the Qt4 GUI. Other times, I connect and it automatically connect me to the existing session. What causes this behavior?
Personally, I don't like this behavior. I'll though explain what's going on:
If no session exists on the server, a new one is created and automatically attached to (well, pretty obvious case.)
If there is a suspended session, there multiple two cases: 1.) the session you currently want to start matches the already existing, suspended session (same settings, including the "application"/"desktop" to start) => this session will then be attached to without prior notification, you will NOT see the session list beforehand 2.) the session to start matches a "running" session on the server. You will be presented with the list (and able to forcefully suspend the running session, if that's what you're after.) 3.) the new session differs in session setting details. In this case, you will get the session list.
I don't like this, because it's inconvenient if you explicitly want to start a new session with the same characteristics. In my opinion, the session list should always be provided if one session (no matter the settings or state) is running on the server.
Mihai