rsnt_translations
56,420
edits
VNC: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 84: | Line 84: | ||
If you want to perform computational tasks within a GUI, please do so on a cluster compute node using the <code>salloc</code> command as described in the Compute Nodes section below. This will ensure the memory and CPU resources on gra-vdi are fully available for interactive graphical visualization purposes by other users when needed. | If you want to perform computational tasks within a GUI, please do so on a cluster compute node using the <code>salloc</code> command as described in the Compute Nodes section below. This will ensure the memory and CPU resources on gra-vdi are fully available for interactive graphical visualization purposes by other users when needed. | ||
== Login | == Login nodes == <!--T:41--> | ||
<!--T:42--> | <!--T:42--> | ||
| Line 124: | Line 124: | ||
Mac or Windows users should click the <i>TigerVNC Viewer</i> application icon on their desktop and enter the '''localhost:port''' information in the "Connection Details" dialogue box that appears. Keep in mind that strict memory and cputime limits apply on cluster login nodes. On Graham, these are 8GB and 1 cpu-hour per process according to <code>ulimit -t -v</code>. If you require more resources, then run your VNC server on the VDI nodes or compute nodes instead as described above and below respectively. | Mac or Windows users should click the <i>TigerVNC Viewer</i> application icon on their desktop and enter the '''localhost:port''' information in the "Connection Details" dialogue box that appears. Keep in mind that strict memory and cputime limits apply on cluster login nodes. On Graham, these are 8GB and 1 cpu-hour per process according to <code>ulimit -t -v</code>. If you require more resources, then run your VNC server on the VDI nodes or compute nodes instead as described above and below respectively. | ||
== Compute | == Compute nodes == <!--T:54--> | ||
<!--T:56--> | <!--T:56--> | ||