https://www.cendio.com/resources/docs/tag-devel/html/config_cluster.html The start of the section that explains how to set up a ThinLinc cluster says: > When configuring ThinLinc servers as a cluster, one needs > to configure both the master server and the agents. The > master server needs configuration for subclusters (even if > there is only one agent) and the agents need to know which > server is the master for access control. Then it goes on to explain that you need to set the parameters master_hostname and login_page. Lastly, it mentions that services need to be restarted. The issue is that the bit about subclusters is unnecessarily obscure. Most clusters will not need to have different subclusters. Most clusters will be simple and only use the "Default" subcluster. How to do that is not trivial to deduce. Below this section follows the large subcluster section.
Something like this would be better: > When configuring ThinLinc servers as a cluster, one needs > to configure both the master server and the agents. The > master server needs a list of agents, and the agents need > to know which server is the master for access control. > > To set up a simple cluster with multiple agents you begin > by adding the addresses of the agents to the configuration > parameter `/vsmserver/subclusters/Default/agents`. > Options for more advanced setups are described in the > Subcluster chapter below.
This is what this section looked like before we added subclusters: > When configuring ThinLinc servers as a cluster, there are two main > configuration options which need to be set, one on the master and one on the > agent(s): > > /vsmserver/terminalservers > > This parameter is configured on the master, and contains a space-separated > list of all agent servers which will be part of this cluster. Only servers in > this list will be considered by the master as available to create sessions on. > See Section 14.2.2, “ Parameters in /vsmserver/ ” for details. > > /vsmagent/master_hostname > ...
