Thanks for you response!
Frankly, trying to remember what i need to do before closing the lid on my Mac is not something i would like to focus on :)
At this point, force quitting the client and then resuming the session is just as good.

I am trying to keep track of this and I dont think it is time related anymore. Sometimes, it happens after the computer sleeps just for a few minutes and other times doesnt happen after the entire night.
This could easily be something with virtualbox networking, but regular ssh sessions survive it or reconnect seamlessly.
Is there any logs that I should look at?

Thanks again.



On Thu, Jul 17, 2014 at 9:40 AM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
Am 17.07.2014 16:33, schrieb Anton Mostovoy:
> I use x2go to connect to Centos VM running in Virtual Box.
> When i put the Mac to sleep over night and open it in the morning, ssh
> session stay connected, but x2go disconnects with a timeout error.
> Incidentally, the x2go client also freezes and I have to force kill it.
> Is it possible to configure the timeout to prevent it from disconnecting?

Maybe one of our Mac gurus will come up with a solution for you, but,
out of curiosity, why don't you just suspend the session in the
x2goclient before suspending the Mac?
That way, when you resume the next morning, you only have to connect to
the existing session again.

My guess is that some x2go component or a program x2go depends on is
monitoring passed time, not passed cpu cycles, and thus determines that
the connection has been without data for too long, once the time and
date settings are updated after the resume, so it bugs out with the
timeout error message.

-Stefan
_______________________________________________
x2go-dev mailing list
x2go-dev@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev