Update home authored by van Vliet's avatar van Vliet
...@@ -1224,7 +1224,7 @@ X DISPLAY # PROCESS ID ...@@ -1224,7 +1224,7 @@ X DISPLAY # PROCESS ID
``` ```
You can/should kill your vncserver session when you are done: You can/should kill your vncserver session when you are done with running your own application:
* vncserver -kill :1 * vncserver -kill :1
``` ```
vncserver -kill :1 vncserver -kill :1
...@@ -1238,10 +1238,11 @@ For example: ...@@ -1238,10 +1238,11 @@ For example:
``` ```
Desktop 'TurboVNC: res-hpc-gpu01.researchlumc.nl:3 (pybvanvliet)' started on display res-hpc-gpu01.researchlumc.nl:3 Desktop 'TurboVNC: res-hpc-gpu01.researchlumc.nl:3 (pybvanvliet)' started on display res-hpc-gpu01.researchlumc.nl:3
``` ```
In this case, port to connect 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 you 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.
### connect from your remote desktop to the vcnserver ### connect from your remote desktop to the vcnserver
... ...
......