I’m still working on a few problems.
A master server distributes sessions across multiple agents. If a user terminates their session (browser being the only session) and no process is running on that user’s agent, the master server still shows the session as connected when using tlctl. When does the master server realize this is incorrect?
Hi @jean!
The server will check/verify session states in a couple of different scenarios. These checks determine if a session is still running and if it’s connected or disconnected.
Firstly, we have a sort of baseline check for all sessions known by the master that runs once every ten minutes. After ending your session, you should see that ThinLinc stops tracking that session when 10 minutes have passed.
Secondly, the server will check the status of a user’s sessions when they log in. If you end your session and then immediately create a new one, you should only see the currently running session being tracked.
If you want, you can also see these events in /var/log/vsmserver.log.
As of ThinLinc version 4.20.0, you can trigger the check earlier if you want, like this: tlctl session list --refresh. 
thank you very much for your reply.
what could be possible disadvanteges, problems be when i let it run every second. would it be a stupid idea?
You’re welcome!
I think that would depend quite a bit on how much traffic your ThinLinc cluster sees overall.
We’re using a limited range of ports for communication between nodes, as is the case with tlctl, and too frequent usage of what you’re asking might risk exhausting that range. This would likely result in your cluster becoming unusable until new ports become available.
Why do you need the session list to be more frequently updated?