Parameters in /vsmagent/

In this section, we will describe all the parameters currently used by the VSM agent.


Public hostname; the hostname that clients are redirected to. If not defined, the agent will use the computer’s IP address. This is the default configuration, and means that ThinLinc does not require DNS to work properly. However, if you are using Network Address Translation (NAT), you must set this parameter to a IP address or DNS name that all clients can connect to. Example:

agent_hostname =

This is the space-separated list of VSM servers that should be allowed to connect to this VSM agent and create new sessions. The localhost is always allowed as well as the IP of the hostname the VSM agent runs on, and the host specified in the /vsmagent/master_hostname parameter.


This subfolder of /vsmagent contains environment variables that should be set in each user’s session. Example:


This will set the TOWN environment variable to Springfield , the LC_CTYPE variable to sv_SE.UTF-8 and the FOOBAR variable to foobar in each user’s session.


xsession is executed via a login shell, which may modify the environment and override values in /vsmagent/default_environment.


The default session size, to be used when clients are not requesting any specific session size.


The maximum display number to be used for ThinLinc sessions on each specific VSM agent host. Default value is 2000.

The maximum ThinLinc sessions allowed on a specific VSM Agent host is /vsmagent/display_max - /vsmagent/display_min.


The lowest display numbers to use for clients. The default is 10, and unless there are other processes needing display numbers, the recommendation is not to change this number. See TCP Ports Used by ThinLinc for an in-depth explanation of port allocation.


The TCP port VSM Agent listen to for incoming requests. This should normally be set to the same value as /vsm/vsm_agent_port.


The lowest port to be used by normal user processes. This may never be lower than /vsmagent/max_session_port . See TCP Ports Used by ThinLinc for an in-depth explanation of port allocation.


If this parameter is true, the users home directory will be automatically created if it doesn’t exist.


When a home directory is created (see parameter /vsmagent/make_homedir above), the mode for the newly created directory will be determined by this parameter.


This parameter specifies the hostname of the master machine, i.e. the machine that runs the VSM server. In a HA setup, this should be the hostname of the IP address that is on the machine that is currently the active node, to ensure that services on the agents that need to access the VSM Server always connects to the machine that is up and running.


The highest port to use for VNC and tunnel ports on the VSM Agent. See TCP Ports Used by ThinLinc for an in-depth explanation of port allocation.


This parameter decides whether the passwords of the users should be saved in order to support Single Sign-On when connecting to servers from the ThinLinc session, for example when running a Windows session.


Extra arguments to pass on to the Xserver Xvnc. One common case is to use -localhost , which makes Xvnc require connections to originate from localhost, thus forcing applications to either be local or use a tunnel (which often also means that the traffic is encrypted). Other examples include -IdleTimeout and -MaxIdleTime. For more information, see Limiting Lifetime of ThinLinc Sessions.


This parameter controls the location of the Xauthority file. Currently, two values are supported: With homedir, the file will be placed in the users home directory. With sessiondir, the file will be placed in the session directory below /var/opt/thinlinc/sessions. The XAUTHORITY environment variable is set accordingly by the VSM agent.