Bug 502 - Inactive client should disconnect
: Inactive client should disconnect
: ThinLinc
: trunk
: PC Linux
: P2 Enhancement
: 4.0.0
Assigned To:
  Show dependency treegraph
Reported: 2004-04-02 13:40 by
Modified: 2012-11-28 11:25 (History)
Acceptance Criteria:



You need to log in before you can comment on or make changes to this bug.

Description From cendio 2004-04-02 13:40:12
It would be nice if the client would automatically disconnect itself from the
session, if no user input has been detected for some time. This is not the same
thing as the session termination stuff in bug 171.
------- Comment #3 From cendio 2011-08-25 16:16:20 -------
Xvnc has had this functionality for some time.
------- Comment #4 From cendio 2011-12-20 14:19:17 -------
(In reply to comment #3)
> Xvnc has had this functionality for some time.

Actually, no: We have three different options that can terminate Xvnc depending
on various conditions, including how long the client has been disconnected.
However, as far as I know, we have no functionality for *disconnecting* the
client after some time. 
------- Comment #5 From cendio 2012-01-04 16:33:54 -------
Actually, we do. 

The IdleTimeout parameter takes a argument in seconds and disconnects a session
that has been idle for that time. Works great from my (limited) testing, but
probably needs mention in the admin guide.

Leaving it open, moving to 3.4.0 for documentation updates.
------- Comment #6 From cendio 2012-07-25 14:30:05 -------
IdleTimeout works for me too; documented in r25533.
------- Comment #7 From cendio 2012-10-18 08:49:50 -------
Documentation is fine.