Dell Wyse Enhanced Ubuntu Linux T50 Manual de usuario Pagina 158

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 220
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 157
Chapter 14. Server Configuration
ships with the tool tl-rsync-all to ensure that configuration changes can be synchronised easily
across all agents in a cluster. See Chapter 13 for more information on how to use this tool.
The tl-rsync-all command should be run on the master server, since it is the master which has a list
of all agents in the cluster (in /vsmserver/terminalservers ). For this reason, it is often useful to
configure the master server as an agent as well, even if it will not be used to host user sessions in general.
This allows the master to be used as a "template" agent, where configuration changes can be made and
tested by an administrator before pushing them out to the rest of the agents in the cluster. In this way,
configuration changes are never made on the agents themselves; rather, the changes are always made on
the master server, and then distributed to the agents using tl-rsync-all.
An example of how one might implement such a system is to configure the master server as an agent
which only accepts sessions for a single administrative user. The steps to do this are as follows:
1. Configure the master as an agent too. On a ThinLinc master, the vsmagent service should already
have been installed during the ThinLinc installation process; make sure that this service is running.
2. Make sure that the master server is not listed in the parameter /vsmserver/terminalservers .
This will ensure that normal users will not be able to create sessions on the master server.
3. Create an administrative user, for example tladmin . Give this user administrative privileges if
required, i.e. sudo access.
4. Make sure that the master server is explicity selected as the agent for tladmin whenever they create
a session. This is done using the parameter /vsmserver/explicit_agentselection . See
Section 14.4.9 for details on this parameter. As an example, the parameter should contain the value
tladmin:master.example.com .
In this way, configuration changes are never made on the agents themselves; rather, the changes are
always made on the master server, and then tested by logging in as the tladmin user. If successful, these
changes are then distributed to the agents using tl-rsync-all.
14.2. Server Configuration Parameters
The ThinLinc server is configured using a number of configuration parameters stored in Hiveconf. For
information about how to access and set the parameters, please refer to Chapter 15. In this chapter, we
will describe the different parameters and their meaning.
The parameters used in ThinLinc are divided into a number of folders, each having zero or more
subfolders. The following folders exist:
/vsm/ contains parameters common to both the VSM agent and the VSM server. This folder normally
resides in /opt/thinlinc/etc/conf.d/vsm.hconf
/vsmagent/ contains parameters specific to the VSM agent. This folder normally resides in
/opt/thinlinc/etc/conf.d/vsmagent.hconf
/vsmserver/ contains parameters specific to the VSM server. This folder normally resides in
/opt/thinlinc/etc/conf.d/vsmserver.hconf
/appservergroups/ contains parameters used by ThinLinc to access application servers. This
folder normally resides in /opt/thinlinc/etc/conf.d/appservergroups.hconf
148
Vista de pagina 157
1 2 ... 153 154 155 156 157 158 159 160 161 162 163 ... 219 220

Comentarios a estos manuales

Sin comentarios