[X2Go-User] Can sessions of one user on different hosts collide?

[Michael DePaulo]

On Fri, Aug 8, 2014 at 10:06 AM, Mike Gabriel
<mike.gabriel at das-netzwerkteam.de> wrote:
> On  Fr 08 Aug 2014 15:02:44 CEST, Les Mikesell wrote:
>
>> On Fri, Aug 8, 2014 at 6:02 AM, Mike Gabriel
>> <mike.gabriel at das-netzwerkteam.de> wrote:
>>>
>>> >
>>>>
>>>> Today, one user ('abbasi') told me, that since one or two weeks, he can
>>>> only
>>>> have one active connection to two of the servers (named 'lucas' and
>>>> 'perrin')
>>>> at a time, while before he could have active connections to both of them
>>>> in
>>>> parallel.
>>>
>>>
>>> this maybe relates to a known NX issue when homes are on NFS. Sessions
>>> become unresponsive there sometimes.
>>>
>>> For X2Go Server 4.0.1.16 (to be released soon) we have moved all NX
>>> related
>>> session stuff from $HOME to $TMP for that very reason.
>>>
>>> The occurences of the same ports are not relevant here, I reckon. Ports
>>> have
>>> to be unique per server, not per user.
>>>
>>
>> Isn't there another issue if the client gets the same display number
>> from both servers?   Something that is likely if you are the first or
>> only connection to two different servers...  With freenx I always
>> randomized the DISPLAY_BASE setting on the servers to minimize that
>> issue but I think the equivalent in x2goserver is buried in one of the
>> scripts.
>
>
> This should be well handled internally by X2Go Client. I know of this odd NX
> problem with the DISPLAY_BASE. In X2Go there should not be such a problem, I
> reckon (unless someone proves me with a test case study).
>
>
> Mike
> [...]

I am unable to reproduce this bug right now, but I believe I have
experienced it numerous times in the past on my home network where the
home directories are stored on GlusterFS (similar enoug hto NFS.) (All
my X2Go Servers mount the gluster volumes using glusterfs, not nfs.) I
recall experiencing this bug yesterday.

I am using the latest stable version of X2Go Client for Windows
(4.0.2.1+hotfix1+build3) on Windows 8.1 64-bit with Update 1.

-Mike#2