Bug 1015 - There is no easy way to disable an agent without changing the configuration
Summary: There is no easy way to disable an agent without changing the configuration
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-09 17:39 CET by Erik Forsberg
Modified: 2022-03-09 17:11 CET (History)
2 users (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Erik Forsberg cendio 2004-12-09 17:39:08 CET 
In some situations, it would be convenient if one could use tladm to disable
more sessions on a specific agent host. This would help if system administration
is going to take place on the host, or if there are suspicions about the host
being broken.
Comment 1 Samuel Mannehed cendio 2022-03-09 17:06:12 CET 
This doesn't necessarily have to be done using tlwebadm. A tool like tlctl could also be used for something like this.
Comment 2 Samuel Mannehed cendio 2022-03-09 17:11:00 CET 
A use case for this is if the admin wants to slowly start emptying an agent before doing upgrades or other changes to the host.

Stopping the 'vsmagent' service would result in the master thinking the agent is down. This, in turn, would when reconnecting to sessions on this agent cause the user to be prompted to abandon the session.

Removing the agent from the configuration will probably achieve the wanted result, but might feel too "permanent" to the admin. The practice of doing this for this use case was documented in bug 7610.
Note You need to log in before you can comment on or make changes to this bug.