ThinLinc ThinLinc ITaP Research Computing provides as an alternative to running an X11 server directly on your computer. It allows you to run graphical applications or graphical interactive jobs directly on Brown through a persistent remote graphical desktop session.
ThinLinc is a service that allows you to connect to a persistent remote graphical desktop session. This service works very well over a high latency, low bandwidth, or off-campus connection compared to running an X11 server locally. It is also very helpful for Windows users who do not have an easy to use local X11 server, as little to no set up is required on your computer. There are two ways in which to use ThinLinc: preferably through the native client or through a web browser. As of 3 December, 2018, if you use Thinlinc from off-campus, you will need to connect to the first.
Installing the ThinLinc native client The native ThinLinc client will offer the best experience especially over off-campus connections and is the recommended method for using ThinLinc. It is compatible with Windows, Mac OS X, and Linux.
Download the ThinLinc client from the. Start the ThinLinc client on your computer. In the client's login window, use desktop.brown.rcac.purdue.edu as the Server.
Use your Purdue Career Account username and password. Click the Connect button. Continue to following section on connecting to Brown from ThinLinc. Using ThinLinc through your web browser The ThinLinc service can be accessed from your web browser as a convenience to installing the native client. This option works with no set up and is a good option for those on computers where you do not have privileges to install software. All that is required is an up-to-date web browser.
Older versions of Internet Explorer may not work. Open a web browser and navigate to.
Log in with your Purdue Career Account username and password. You may safely proceed past any warning messages from your browser. Continue to the following section on connecting to Brown from ThinLinc. Connecting to Brown from ThinLinc. Once logged in, you will be presented with a remote Linux desktop running directly on a cluster front-end. Open the terminal application on the remote desktop.
Figure 2.1 gives an overview of the ThinLinc architecture. Several different clients can be used to connect to a ThinLinc system. Clients are available for Linux, OSX, and Windows, as well as a client for any web browser with support for HTML5. Popular Alternatives to ThinLinc for Windows, Mac, Android, iPhone, Linux and more. Explore 25+ apps like ThinLinc, all suggested and ranked by the AlternativeTo user community. Remmina is a remote desktop client written in GTK+, aiming to be useful for system administrators and travellers, who need to work with lots of remote computers in.
Once logged in to the Brown head node, you may use graphical editors, debuggers, software like Matlab, or run graphical interactive jobs. For example, to test the X forwarding connection issue the following command to launch the graphical editor gedit: $ gedit. This session will remain persistent even if you disconnect from the session. Any interactive jobs or applications you left running will continue running even if you are not connected to the session. Tips for using ThinLinc native client. To exit a full screen ThinLinc session press the F8 key on your keyboard ( fn + F8 key for Mac users) and click to disconnect or exit full screen. Full screen mode can be disabled when connecting to a session by clicking the Options button and disabling full screen mode from the Screen tab.
The ThinLinc Server Bundle from after registering with them. Installation of the: unzip tl-4.8.0-server.zip cd tl-4.8.0-server./install-server NOTICE:. SELinux systems (RHEL/CentOS) require settings of files in /opt/thinlinc, so installation must be in that directory (soft-links will break the setup). CentOS: A warning will be issued that CentOS 7 is not supported. To rerun the configuration setup script do: /opt/thinlinc/sbin/tl-setup Many additional RPMs will be installed on the system, and configuration of the firewall and SELinux. Read the page about installation of ThinLinc on an SELinux-enabled platform. The SELinux module and other policy changes performed can be examined in /opt/thinlinc/share/selinux.
Execute the command: /opt/thinlinc/share/selinux/install to reapply ThinLinc's policy changes. If you don't run an Apache web-server, some installation warnings will be issued. A web-server is actually not required for normal operation, for more on that topic see. By default there are 5 user licenses (hard limit is 6). We can get additional licenses from Bernd Dammann (DTU Compute). License installation instructions are in:. Transfer each file to your ThinLinc master server and place it in /opt/thinlinc/etc/licenses/.
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. Check the licenses by: /opt/thinlinc/sbin/tl-show-licenses See also the log file /var/log/thinlinc-user-licenses.
Network setup is documented in. Several firewall ports are opened by the Server installation, see the service files /etc/firewalld/services/tl. which are referred to in /etc/firewalld/zones/public.xml. The page and say that the following TCP ports must be opened in the firewall of the VSM server:. 22: SSH Daemon. 300: ThinLinc HTML5 Browser Client.
Thinlinc Client Download
904: VSM Agent. 1010: ThinLinc Administration Interface (tlwebadm). 9000: VSM server If users are supposed to be able to connect using a web browser, using the HTML5 Browser Client, they must be able to connect to port 300 on both the VSM server and on all VSM agents. To list the current firewall configuration run: iptables-save. Even though the ThinLinc server apparently has installed correctly, clients are unable to connect to it but give an error message: ThinLinc login failed (No agent server was available) In the /var/log/messages syslog you may see a message like: python: SELinux is preventing /u/opt/thinlinc/libexec/tl-session from using the transition access on a process. Plugin catchall (100.
Confidence) suggests. If you believe that tl-session should be allowed transition access on processes labeled unconfinedt by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: grep tl-session /var/log/audit/audit.log audit2allow -M mypol; semodule -i mypol.pp You should make sure that has been installed in the default /opt/thinlinc directory (soft-links not permitted).
If you want to check if SELinux is causing troubles, you can temporarily turn SELinux off and on by: setenforce 0 # Turn SELinux off setenforce 1 # Turn SELinux on.