Am 17.03.2016 um 15:34 schrieb Real, Elizabeth (392K): > Hello, > > I have a clustered linux system (node1 – node24) which we access via a > FQDN, the problem when using x2go client using KDE is that when you > _suspend_ an active session then log back in, x2go does not alert you > that there is a suspended session, you are able to log in but you are > connected to a different node. > > What is your approach at being able to resume an active KDE session when > connecting to a linux clustered system? > > x2go server: RHEL7, x2go version 4.0.1 > x2go client: RHEL7, x2go version 4.0.5
Sounds like you should be using the x2go session broker - configuring that, however, is currently not for the faint of heart, especially when you want to get session resume working. I would strongly suggest contracting us or one of the other companies providing commercial X2Go support, as it is unlikely that someone runs this in a home setup and is willing and able to help out voluntarily. Feel free to contact us off-list at [email protected] or one of the other companies listed at: http://wiki.x2go.org/doku.php/doc:professional-support Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
signature.asc
Description: OpenPGP digital signature
_______________________________________________ x2go-dev mailing list [email protected] http://lists.x2go.org/listinfo/x2go-dev
