VNC Server - bwUniCluster 2.0: Difference between revisions
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Start a VNC Server on the bwUniCluster 2.0 == |
== Start a VNC Server on the bwUniCluster 2.0 == |
||
To start a VNC Server on the bwUniCluster 2.0 you must log into the cluster with your username and password as usual. Please do not start the VNC Server on a login node but request an interactive job using for example the following command: |
To start a VNC Server on the bwUniCluster 2.0 you must log into the cluster with your username and password as usual. Please do not start the VNC Server on a login node but request an [[BwUniCluster_2.0_Batch_Queues#Interactive_Jobs|interactive job]] using for example the following command: |
||
$ salloc -p single -n 1 -t 120 --mem=5000 |
$ salloc -p single -n 1 -t 120 --mem=5000 |
||
Latest revision as of 20:40, 8 October 2020
Start a VNC Server on the bwUniCluster 2.0
To start a VNC Server on the bwUniCluster 2.0 you must log into the cluster with your username and password as usual. Please do not start the VNC Server on a login node but request an interactive job using for example the following command:
$ salloc -p single -n 1 -t 120 --mem=5000
Now start the VNC Server on the assigned compute node as follows:
$ module load vis/tigervnc $ run_vncserver
If you start a VNC Server for the first time you will be asked to set a password which will be required for clients trying to access your VNC desktop. Use a strong password because otherwise an attacker could take control of your VNC session.