
Chapter 14. Server Configuration
The log level configured can be seen as a barrier. If the log level is set to for example INFO, log
messages with a level of INFO or higher are let through. If the log level instead is set to DEBUG2, all log
messages are let through, since all log levels are higher than DEBUG2.
There is one default loglevel, and one loglevel per sublogger defined. If the log level for a sub level is set
to a lower value than the default loglevel, more information will be written by that specific sublogger.
The default loglevel is configured in the logging/defaultlevel parameter. Each sublogger’s level
can then be configured by setting the parameters under the logging/levels folder.
14.3.1.4. Summary
The default logging configuration is summarized in Table 14-2.
Table 14-2. Default Log Behaviour
Component Default Behaviour Log Configuration Hive
Folder
VSM server Log to /var/log/vsmserver.log /vsmserver/logging
VSM agent Log to /var/log/vsmagent.log /vsmagent/logging
Web Administration Interface Log to /var/log/tlwebadm.log /tlwebadm/logging
Web Access (HTML5) Log to /var/log/tlwebaccess.log /webaccess/logging
14.3.2. Per-Session Logging
Each Session writes what is written to standard output and standard error output to a file named
xinit.log which is located in the session directory for a specific session. For example, the log for the
last session of the user pelle is located in /var/opt/thinlinc/sessions/pelle/last/. This log
contains for example output written by software run in the session, but it also has some output from
ThinLinc software that is run by the user.
14.4. Customizing the User’s Session
In this section, we will describe how the session startup in ThinLinc can be customized.
14.4.1. Session startup - the big picture
The session setup is constructed to be easy to use and configure yet still easy to customize for advanced
use cases.
158
Komentáře k této Příručce