Bug 284 - Limit the number of concurrent users or sessions (per cluster, per agent)
Summary: Limit the number of concurrent users or sessions (per cluster, per agent)
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Target Milestone: LowPrio
Assignee: Peter Åstrand
: 5966 (view as bug list)
Depends on:
Reported: 2003-05-07 10:49 CEST by Peter Åstrand
Modified: 2022-10-04 10:12 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2003-05-07 10:49:37 CEST
It might be useful to be able to limit the number of concurrent users. This has
nothing to do with licensing, but might be useful anway. For example, a system
administrator might want to reduce the server load. 

It should be easy to implement this, since the vsmserver already has knowledge
of the number of concurrent users. All we need to do is to add a parameter to
vsmserver.conf, and use it in vsmserver.
Comment 1 Peter Åstrand cendio 2004-04-05 09:33:03 CEST
To be useful, this should probably be settable *per*agent*; not per cluster.
That's a bit harder than just checking this on the VSM server. 

Perhaps not very useful after all. Re-targeting. 
Comment 2 Karl Mikaelsson cendio 2016-11-08 14:22:16 CET
*** Bug 5966 has been marked as a duplicate of this bug. ***
Comment 5 Pierre Ossman cendio 2020-10-09 09:57:07 CEST
Also note bug 4429 which may remove some of the need for this feature, depending on how it turns out.
Comment 6 Pierre Ossman cendio 2020-10-29 10:33:40 CET
A use case that's been described to us is users making heavy use of GPUs. The amount of RAM is a limiting factor and many applications are designed to get exclusive access and don't gracefully deal with memory running out.

So our users want to work around this by limiting the number of users per agent, and hence per GPU. In some cases to the extreme of one user per agent. For them it is a better user experience to be denied a session than applications crashing or erroring out.
Comment 11 Pierre Ossman cendio 2022-10-04 10:06:31 CEST
Another use case is security, where the admin wants to minimize the risk of data leaking between users by only having a single user per system.

Note that this assumes that there is no substantial risk of things being left behind by a user as an agent can be reused for a different user once the first user logs out.

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