On Mon, 2011-04-11 at 13:35 +0200, Mike Gabriel wrote:
<snip>
What you can do is start an x2go session on your server, suspend this
session and resume it again (from some other client).If you cannot find menu items for suspending sessions, you can open a
shell and run the following commands:x2golistsessions -> will show your current sessions on that server
The x2golistsessions command gives you the session id. It should look
like ,,mike-59-1302521405_stDGNOME_dp24'', it is the second field in
each line reported by x2golistsessions.With the session id you can suspend your session:
x2gosuspend-session mike-59-1302521405_stDGNOME_dp24
If you then login to the server again then you should be able to
resume this session (Fortsetzen/fortfahren in German, not sure which
one is used).Of course, this scripting stuff is a little awkward. If you install
the package x2gognomebindings (for GNOME) or x2goplasmoid (for KDE4)
there should be a menu item that allows to suspend a session. With
x2goplasmoid I have seen situations that this does not work reliably,
but with GNOME there will definitely be a menu item in ,,System'' menu. <snip> We elected to create an icon which called the x2gosuspend-session-gnome script. We found when we installed x2gokdebindings that it stole the end session button for terminate (which was fine) and the lock desktop button for suspend which was definitely not fine because we wanted users to be able to lock and step away from their virtual desktops. Thanks - John