rsnt_translations
56,420
edits
VNC: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
<!--T:10--> | <!--T:10--> | ||
Download and run the latest stable vncviewer64-x.y.z.exe version package installer from [https://sourceforge.net/projects/tigervnc/files/stable/ the official download page] ( for example <code>vncviewer64-1.12.0.exe</code>). Make sure you download the viewer and not the server. To create secure tunnels from your desktop to the vncserver as described in the sections below, you will need to open a terminal window and run the | Download and run the latest stable vncviewer64-x.y.z.exe version package installer from [https://sourceforge.net/projects/tigervnc/files/stable/ the official download page] ( for example <code>vncviewer64-1.12.0.exe</code>). Make sure you download the viewer and not the server. To create secure tunnels from your desktop to the vncserver as described in the sections below, you will need to open a terminal window and run the SSH command. This may be done using PowerShell standard on Windows 10 since the 1809 October update. | ||
== MacOS == <!--T:12--> | == MacOS == <!--T:12--> | ||
| Line 93: | Line 93: | ||
<!--T:44--> | <!--T:44--> | ||
1) Specify a 1hr ( | 1) Specify a 1hr (3600 sec) time limit for your server (or more as required): | ||
<!--T:164--> | <!--T:164--> | ||
| Line 133: | Line 133: | ||
<!--T:60--> | <!--T:60--> | ||
Before starting your VNC server, log in to a cluster (such as Cedar) and create an allocation on a compute node using the <code>salloc</code> | Before starting your VNC server, log in to a cluster (such as Cedar) and create an allocation on a compute node using the <code>salloc</code> command (a 24hr maximum time limit applies). For example, to request an [[Running_jobs#Interactive_jobs|interactive job]] using 4 CPUs and 16GB of memory you could use the command: | ||
<!--T:141--> | <!--T:141--> | ||
| Line 183: | Line 183: | ||
<!--T:68--> | <!--T:68--> | ||
<b>2) | <b>2) Set up a SSH tunnel to the VNC server</b> | ||
<!--T:70--> | <!--T:70--> | ||
| Line 203: | Line 203: | ||
<!--T:78--> | <!--T:78--> | ||
If you have a Linux desktop, open a new local terminal window and tell your VNC client to connect to '''localhost:port'''. The following example uses the TigerVNC <code>vncviewer</code> command to connect to the running VNC server on cdr768. You will be prompted for the VNC password that you | If you have a Linux desktop, open a new local terminal window and tell your VNC client to connect to '''localhost:port'''. The following example uses the TigerVNC <code>vncviewer</code> command to connect to the running VNC server on cdr768. You will be prompted for the VNC password that you set up earlier in order to connect. | ||
<!--T:146--> | <!--T:146--> | ||
| Line 347: | Line 347: | ||
<!--T:124--> | <!--T:124--> | ||
For accelerated OpenGL to work, it is necessary to adjust compiled binaries to | For accelerated OpenGL to work, it is necessary to adjust compiled binaries to preload an appropriate version of the "vglfaker.so" library from VirtualGL. This has already been done for software modules available on gra-vdi and any OpenGL based packages you build/install via nix. It is, however, something that has to be done for any pre-built software you download or any codes you compile without using nix. | ||
<!--T:126--> | <!--T:126--> | ||
| Line 359: | Line 359: | ||
<!--T:128--> | <!--T:128--> | ||
Note that it is also possible to | Note that it is also possible to preload ''vglfaker.so'' via the <code>LD_PRELOAD</code> environment variable. This is generally a bad idea as it applies indiscriminately to all binaries, and those that require a different ''vglfaker.so'' than that set in <code>LD_PRELOAD</code> will then fail; however, it can be used safely in some cases in wrapper scripts. | ||
== CVMFS == <!--T:130--> | == CVMFS == <!--T:130--> | ||
<!--T:132--> | <!--T:132--> | ||
Alliance software modules reside under /cvmfs and are available by default when you log into Graham, Cedar and Béluga. | Alliance software modules reside under /cvmfs and are available by default when you log into Graham, Cedar and Béluga. However, these modules are not loaded by default when you connect into gra-vdi over tigervnc. To load them open a terminal window and run the following: | ||
<!--T:155--> | <!--T:155--> | ||