On 01.02.2016 03:51 PM, Reinhard Tartler wrote:
> At my new employer, I've convinced our system administrators to give x2go a
> shot. They noticed that it is included in EPEL6 and installed it on CentOS6
> workstations. This test went pretty well so far. Unfortunately, that installed
> version 3.5 of x2go, which as I understand it is not the best impression that we
> can make. We deployed it with the sqlite back end and I noticed that the
> cleansessions daemon appears to crash from time to time. This is very annoying
> in particular given that we reboot our login nodes about once to twice a year
> and the effects are rather unintuitive to debug. My hope is that x2go 4 is more
> resilient here (but I admit that I didn't check myself).
>
> In any case, I suppose it is in everyone's best interest to prefer a newer
> version of x2go than currently in EPEL6
> (cf. https://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/x2goagent.html) -
> because otherwise, EPEL user are not going to receive any work towards getting
> bugfixes.

You're confusing nx-libs, which has a 3.5.x versioning scheme, with the
x2goserver versioning scheme.

x2goagent is part of nx-libs and 3.5.0.32 is the newest stable release I made.