... | @@ -1351,6 +1351,90 @@ nvidia-smi |
... | @@ -1351,6 +1351,90 @@ nvidia-smi |
|
+-----------------------------------------------------------------------------+
|
|
+-----------------------------------------------------------------------------+
|
|
```
|
|
```
|
|
|
|
|
|
|
|
### create a vncserver setup and start a vncserver session
|
|
|
|
If you are setting up a vcnserver session for the first time, it will ask you a few questions and after that you have to adapt the configuration and startup file:
|
|
|
|
|
|
|
|
```
|
|
|
|
vncserver
|
|
|
|
|
|
|
|
You will require a password to access your desktops.
|
|
|
|
|
|
|
|
Password:
|
|
|
|
Verify:
|
|
|
|
Would you like to enter a view-only password (y/n)? n
|
|
|
|
|
|
|
|
Desktop 'TurboVNC: res-hpc-lo02.researchlumc.nl:1 (username)' started on display res-hpc-lo02.researchlumc.nl:1
|
|
|
|
|
|
|
|
Creating default startup script /home/username/.vnc/xstartup.turbovnc
|
|
|
|
Starting applications specified in /home/username/.vnc/xstartup.turbovnc
|
|
|
|
Log file is /home/username/.vnc/res-hpc-lo02.researchlumc.nl:1.log
|
|
|
|
|
|
|
|
```
|
|
|
|
You should choose a strong password, the password should not be the same as the user login password.
|
|
|
|
|
|
|
|
Kill the vncserver connection:
|
|
|
|
* vncserver -kill :1
|
|
|
|
|
|
|
|
Now adapt the **xstartup.turbovnc** file:
|
|
|
|
* vi $HOME/.vnc/xstartup.turbovnc
|
|
|
|
```
|
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
unset SESSION_MANAGER
|
|
|
|
unset DBUS_SESSION_BUS_ADDRESS
|
|
|
|
XDG_SESSION_TYPE=x11; export XDG_SESSION_TYPE
|
|
|
|
|
|
|
|
exec icewm-session
|
|
|
|
```
|
|
|
|
|
|
|
|
Adapt/create a **turbovncserver.conf** file for the vncserver with some useful settings:
|
|
|
|
* vi $HOME/.vnc/turbovncserver.conf
|
|
|
|
```
|
|
|
|
$geometry="1280x1024"
|
|
|
|
$depth=24
|
|
|
|
```
|
|
|
|
Now start the vncserver:
|
|
|
|
```
|
|
|
|
vncserver
|
|
|
|
|
|
|
|
Desktop 'TurboVNC: res-hpc-lo02.researchlumc.nl:1 (username)' started on display res-hpc-lo02.researchlumc.nl:1
|
|
|
|
|
|
|
|
Starting applications specified in /home/username/.vnc/xstartup.turbovnc
|
|
|
|
Log file is /home/username/.vnc/res-hpc-lo02.researchlumc.nl:1.log
|
|
|
|
```
|
|
|
|
You can list you vncserver session with the following command:
|
|
|
|
* vncserver -list
|
|
|
|
```
|
|
|
|
vncserver -list
|
|
|
|
TurboVNC sessions:
|
|
|
|
|
|
|
|
X DISPLAY # PROCESS ID
|
|
|
|
:1 33915
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
You can/should kill your vncserver session when you are done with running your own application:
|
|
|
|
* vncserver -kill :1
|
|
|
|
```
|
|
|
|
vncserver -kill :1
|
|
|
|
Killing Xvnc process ID 47947
|
|
|
|
```
|
|
|
|
|
|
|
|
#### vncserver and port numbers
|
|
|
|
Everytime someone start a vcnsession and there is already a vncsession running, the port number will increase.
|
|
|
|
The first connection will be on **:1** which is port 5900 + 1, where the port 5900 is the standard port number for VNC.
|
|
|
|
For example:
|
|
|
|
```
|
|
|
|
Desktop 'TurboVNC: res-hpc-gpu01.researchlumc.nl:3 (username)' started on display res-hpc-gpu01.researchlumc.nl:3
|
|
|
|
```
|
|
|
|
In this case, the port to connect to is number **3**.
|
|
|
|
So you connect to "res-hpc-gpu01.researchlumc.nl:3".
|
|
|
|
|
|
|
|
You can always list your own open vnc session with the **vncserver -list** command.
|
|
|
|
|
|
|
|
Remember to kill you vnc session when you are done running your own application.
|
|
|
|
|
|
|
|
|
|
### Remote visualization with a "reverse SSH tunnel"
|
|
### Remote visualization with a "reverse SSH tunnel"
|
|
|
|
|
|
With a reverse SSH tunnel you can make a quick connection to a remote desktop.
|
|
With a reverse SSH tunnel you can make a quick connection to a remote desktop.
|
... | | ... | |