Chapter 4. License Handling
4.1. Overview
To run a session against a ThinLinc cluster, the server must be equipped with license files. The license
files specify the number of concurrent users the cluster is allowed to run.
If no license files are installed on the cluster, a maximum of ten concurrent users are allowed.
Each cluster can have one or several license files. Each file contains licenses for a specific number of
concurrent users. When the VSM Server starts up, it reads all license files and creates a sum of the
number of concurrent users allowed based on the licenses from all files.
License files have one soft and one hard limit. When the soft limit is reached, new sessions can still be
started, but a license violation will be logged and sent to the administrator (see Section 4.4). If however
the hard limit has been reached, new sessions cannot be started. The purpose of this system is to allow
growing organisations some time to adapt the number of licenses to a growing number of concurrent
sessions, avoiding loss of production.
4.2. License Counting
One license is required for each pair of (username,client hardware). This means that if a user runs
several sessions from the same client, only one license is used. If the same user runs multiple concurrent
sessions from different client hardware, multiple licenses are required by the user.
4.3. Location and format of License Files
License files are delivered either in the form of text files (filename extension .license) or ZIP files
(filename extension .zip). Transfer each file to your ThinLinc cluster and place it in
/opt/thinlinc/etc/licenses. Make sure that the transfer of the files uses binary mode, or the
license file might not be verifiable. We recommend transferring via scp or sftp.
After adding new license files, either restart VSM Server by running /opt/thinlinc/libexec/service
vsmserver restart or wait until the VSM Server automatically reads in the new licenses, something that
happens once every 12 hours.
Note: When running VSM Server in a High Availability setup (see Chapter 6), license files should be
copied to /opt/thinlinc/etc/licenses on both nodes.
4.4. Log Files and E-mail Messages
ThinLinc logs user license violations to the file /var/log/thinlinc-user-licenses. Other
license-related messages are logged to /var/log/vsmserver.log.
19
Komentarze do niniejszej Instrukcji