close #32 thanks

Hello,

we are very hopeful that X2Go issue #32 reported by you has been resolved in the new release (4.0.1.0) of the X2Go source project »src:x2goserver«.

You can view the complete changelog entry of src:x2goserver (4.0.1.0) below, and you can use the following link to view all the code changes between this and the last release of src:x2goserver.

http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=51551c467a7dca4be4fb890f3c6a29e7173d05cc;hp=498e2b7e5a8fa9216a57f2234f57f6a6fa7ed261

If you feel that the issue has not been resolved satisfyingly, feel free to reopen this bug report or submit a follow-up report with further observations described based on the new released version of src:x2goserver.

Thanks a lot for contributing to X2Go!!!

light+love X2Go Git Admin (on behalf of the sender of this mail)

X2Go Component: src:x2goserver Version: 4.0.1.0 Status: RELEASE Date: Fri, 07 Jun 2013 23:07:40 +0200 Fixes: 32 Changes: x2goserver (4.0.1.0) RELEASED; urgency=low .

• New upstream version (4.0.1.0):
  • Make x2gomountdirs / x2goumount-session UNC path aware.
  • Add support to x2gocleansessions to suspend session via state changes in the session DB.
  • Add support for terminating sessions via the session DB.
  • Raise the frequency of the x2gocleansessions loop to every two seconds.
  • Send SIGKILL to blocked X-Server (x2goagent) processes, if they do not disappear within 20secs. (Fixes: #32).