Where Does ThinLinc Client Store Config?
ThinLinc Client reads tlclient.conf from home .thinlinc with global defaults beside the install. Windows uses the registry.
Last updated
ThinLinc Client layers config from global to user to command line. Linux reads the install etc file first, then the home .thinlinc copy which wins. macOS swaps the global path into Application Support. Windows stores the same names in registry hives.
A config file flag points at arbitrary .tlclient files for kiosk or lab setups. The client log sits beside the user config on Unix and in temp on Windows, truncated each launch. Mandatory admin files can lock individual parameters.
Where ThinLinc stores this, by platform
/home/<username>/.thinlinc/tlclient.conf
User config in plain key value form. Global defaults in opt thinlinc etc lose to this file.
/home/<username>/.thinlinc/tlclient.log
Session log, truncated every launch. Raise debug level in options for connection faults.
HKEY_CURRENT_USER\Software\Cendio\ThinLinc\tlclient
Windows settings under the vendor key. HKLM holds globals, HKCU the user layer. Same parameter names as Unix.
/Library/Application Support/ThinLinc Client/tlclient.conf
Global config on Mac. User file keeps the same home relative path as Linux.
Frequently asked questions
How do I change ThinLinc client settings by hand?
Edit the user conf file on Linux and Mac, or the HKCU values on Windows. The admin guide lists every parameter name and valid value.
Where is the ThinLinc client log?
Launch once with the debug flag or raise the level in options. The log truncates on every start, so grab it before reconnecting.
Notice an outdated path? Let us know.