Is it possible to limit the lifetime of a ThinLinc session?

One benefit of terminal server solutions like ThinLinc is the ability to have persistent sessions. Users can log in, start a job, disconnect at any time, and come back later to pick up where they left off. This is especially useful for long-running, non-interactive jobs which don’t require constant supervision.

However, session persistence is not always desirable. Sometimes users might finish their job, but rather than logging out afterwards, they simply disconnect from their ThinLinc session. This leaves the session running on the server, unnecessarily consuming ThinLinc licenses and potentially system resources as well. While it may be convenient to keep the session alive for short periods of time - for example, to allow users to move locations or stop work for the weekend - leaving unused sessions running for weeks or months can be wasteful.

Administrators can configure ThinLinc to terminate sessions automatically when certain conditions are met, such as no client being connected for a certain period of time. You can find a list of available options and how to set them in the ThinLinc Administrator’s Guide here:

When setting these options make sure to put user experience first; nobody wants to have their session terminated halfway through a job. But setting them appropriately for your specific use-case can make your systems more efficient and maximise resource usage within your organisation.

1 Like