Bug 4256 - changing how the master identifies agents can cause lost sessions
Summary: changing how the master identifies agents can cause lost sessions
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Agent (show other bugs)
Version: 3.2.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Peter Åstrand
Depends on:
Reported: 2012-04-12 10:00 CEST by Pierre Ossman
Modified: 2023-12-14 14:25 CET (History)
1 user (show)

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2012-04-12 10:00:34 CEST
Currently we identify an agent based on what it is called in /vsmserver/terminalservers. This is not terribly robust as simply switching between IP and a hostname, or from a short name to a FQDN, is sufficient to confuse the master and think this is a different agent. More complex things like giving an agent a new name/IP is also problematic.

We should start identifying agents on something that is more persistent than their network identity. A simple solution is that an agent simply generates a random id and stores it on disk. This id can then be included in the protocol and the master should be able to keep track of each agent.

We should probably store this id in /var/opt/thinlinc to avoid getting it rsync:ed between agents.

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