It should be possible to set up ThinLinc so that sessions are automatically terminated if the user is inactive for a certain time. Moreon, some customers have requested that this should only be done for sessions created "from the Internet, not from inhouse". It may be possible to solve this by using the terminal ID. If the terminal is known (exists in the LDAP database), it may be allowed to have inactive sessions for an unlimited time.
Windows 2003 has three settings for this: 1. Disconnected session limit 2. Active session limit 3. Idle session limit To me, it seems unnecessary to distinguish between case 1 and 3 (eg. implement a idle timeout that works regardless of if any client is connected or not.) Case 2 is not covered by this bug, and has not been requested by customers. So, what does "idle" mean? I cannot think of anything else but "keyboard or mouse input". Meaning: This bug could be solved by implementing a mechanism that terminates sessions that has not had any keyboard or mouse input in a certain time. The only process that knows this is Xvnc, so it must be involved in some way.
*** Bug 222 has been marked as a duplicate of this bug. ***
Solved during fix of bug 704. There's room for improvements, however. For example, when the idle or active timeout happens, it would be nice if the user could be notified of this via a popup-window. Windows does this.
Closing this as duplicate for the original problem, that idle sessions weren't disconnected. The notification is a broader problem that will be handled by bug 7273. *** This bug has been marked as a duplicate of bug 704 ***