Update home authored by van Vliet's avatar van Vliet
...@@ -1241,7 +1241,7 @@ Desktop 'TurboVNC: res-hpc-gpu01.researchlumc.nl:3 (username)' started on displa ...@@ -1241,7 +1241,7 @@ Desktop 'TurboVNC: res-hpc-gpu01.researchlumc.nl:3 (username)' started on displa
In this case, the port to connect to is number **3**. In this case, the port to connect to is number **3**.
So you connect to "res-hpc-gpu01.researchlumc.nl:3". So you connect to "res-hpc-gpu01.researchlumc.nl:3".
You can always list you own open vnc session with the **vncserver -list** command. 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. Remember to kill you vnc session when you are done running your own application.
...@@ -1302,7 +1302,7 @@ nvidia-smi ...@@ -1302,7 +1302,7 @@ nvidia-smi
* Solution: stop the program and start it again. The second time it should run at normal/smooth speed * Solution: stop the program and start it again. The second time it should run at normal/smooth speed
##### Remember: ##### Remember:
* kill you own vnc session with "vncserver -kill:[port number] when you are done with your application * kill your own vnc session with "vncserver -kill:[port number] when you are done with your application
* do not close the **bash shell** which you got with the "srun" command before you are done with your application * do not close the **bash shell** which you got with the "srun" command before you are done with your application
* if you close your bash shell (srun), the vnc session will be terminated. * if you close your bash shell (srun), the vnc session will be terminated.
You will see something like if you run the "vncserver -list" command: You will see something like if you run the "vncserver -list" command:
... ...
......