4 merge requests!368Update prace.md to document the change from qprace to qprod as the default...,!367Update prace.md to document the change from qprace to qprod as the default...,!366Update prace.md to document the change from qprace to qprod as the default...,!323extended-acls-storage-section
**Virtual Network Computing** (**VNC**) is a graphical [desktopsharing][a] system that uses the [Remote Frame Buffer protocol (RFB)][b] to remotely control another [computer][c]). It transmits the [keyboard][d] and [mouse][e] events from one computer to another, relaying the graphical [screen][f] updates back in the other direction, over a [network][g].
Virtual Network Computing (VNC) is a graphical desktop-sharing system that uses the [Remote Frame Buffer][a] protocol (RFB) to remotely control another computer. It transmits the keyboard and mouse events from one computer to another, relaying the graphical screen updates back in the other direction, over a network.
Vnc-based connections are usually faster (require less network bandwidth) than [X11][1] applications forwarded directly through SSH.
The recommended clients are [TightVNC][h] or [TigerVNC][i] (free, open source, available for almost any platform).
The recommended clients are [TightVNC][b] or [TigerVNC][c] (free, open source, available for almost any platform).
In this chapter, we show how to create an underlying SSH tunnel from your client machine to one of our login nodes. Then, how to start your own VNC server on our login node and finally how to connect to your VNC server via the encrypted SSH tunnel.
...
...
@@ -123,7 +123,7 @@ kill 2022
```
!!! note
You can watch the instruction video on how to make a VNC connection between a local Ubuntu desktop and the IT4I Salomon cluster [here][k].
You can watch the instruction video on how to make a VNC connection between a local Ubuntu desktop and the IT4I Salomon cluster [here][e].
## Windows Example of Creating a Tunnel
...
...
@@ -140,15 +140,15 @@ tcp 0 0 127.0.0.1:5961 0.0.0.0:* LIST
### PuTTY
On the PuTTY Configuration screen, go to Connection->SSH->Tunnels to set up the tunnel.
On the PuTTY Configuration screen, go to _Connection->SSH->Tunnels_ to set up the tunnel.
Fill the Source port and Destination fields. **Do not forget to click the Add button**.
Fill the _Source port_ and _Destination_ fields. **Do not forget to click the _Add_ button**.
### WSL (Bash on Windows)
[Windows Subsystem for Linux][j] is another way to run Linux software in a Windows environment.
[Windows Subsystem for Linux][d] is another way to run Linux software in a Windows environment.
At your machine, create the tunnel:
...
...
@@ -223,7 +223,7 @@ or:
The very same methods as described above may be used to run the GUI applications on compute nodes. However, for maximum performance, follow these steps:
Open a Terminal (Applications -> System Tools -> Terminal). Run all the following commands in the terminal.
Open a Terminal (_Applications -> System Tools -> Terminal_). Run all the following commands in the terminal.
...
...
@@ -233,7 +233,7 @@ Allow incoming X11 graphics from the compute nodes at the login node:
$xhost +
```
Get an interactive session on a compute node (for more detailed info [look here][4]). Use the **-v DISPLAY** option to propagate the DISPLAY on the compute node. In this example, we want a complete node (16 cores in this example) from the production queue:
Get an interactive session on a compute node (for more detailed info [look here][4]). Use the `-v DISPLAY` option to propagate the DISPLAY on the compute node. In this example, we want a complete node (16 cores in this example) from the production queue:
