cc_staff
1,857
edits
VNC: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 247: | Line 247: | ||
<!--T:90--> | <!--T:90--> | ||
To reset your VNC server password use the <code>vncpasswd</code> command: | |||
= | <source lang="bash"> | ||
[gra-login1:~] vncpasswd | |||
Password: | |||
Verify: | |||
Would you like to enter a view-only password (y/n)? n | |||
</source> | |||
Optionally you can completely remove your VNC configuration (including your password) by deleting your <code>~/.vnc</code> directory. The next time you run <code>vncserver</code> you will be prompted to set a new password. | |||
== | == Killing vncserver == <!--T:96--> | ||
<!--T:98--> | <!--T:98--> | ||
If a | If a vncserver is no longer needed terminate it with <code>vncserver -kill :DISPLAY#</code> as shown here: | ||
<source lang="bash"> | <source lang="bash"> | ||
| Line 268: | Line 268: | ||
TigerVNC server sessions: | TigerVNC server sessions: | ||
X DISPLAY# PROCESS ID | |||
:44 27644 | :44 27644 | ||
| Line 275: | Line 275: | ||
</source> | </source> | ||
<!--T:99--> | <!--T:99--> | ||
If you have multiple vncservers running, you | If you have multiple vncservers running on a node, you may kill them all by running: <code>pkill Xvnc -u $USER</code>. | ||
== Multiple | == Multiple connections == <!--T:100--> | ||
<!--T: | <!--T:102--> | ||
Any vncserver(s) running under your username can be listed with <code>vncserver -list</code>. To reconnect to a particular vncserver on a login node 1) re-establish a port forwarded tunnel 2) run the vncviewer command again. It is possible to start multiple remote vncviewer connections to an existing vncviewer desktop. For example to connect from a second home machine while leaving the original vncviewer connection running at the office. To do this requires starting your vncserver with a special option <code>vncserver -AlwaysShared</code> otherwise addtional vncviewer connections will (by default) close the original vncviewer connection. | |||
== Failures to connect == <!--T:102--> | == Failures to connect == <!--T:102--> | ||
<!--T: | <!--T:104--> | ||
Repeated failure attempts to establish a new vncserver/vncviewer connection may be due to an old ssh tunnel still running on your desktop tying up ports. To identify and kill any such tunnels, open a terminal window on your desktop and run <code>ps ux | grep ssh</code> followed by <code>kill PID</code>. | Repeated failure attempts to establish a new vncserver/vncviewer connection may be due to an old ssh tunnel still running on your desktop tying up ports. To identify and kill any such tunnels, open a terminal window on your desktop and run <code>ps ux | grep ssh</code> followed by <code>kill PID</code>. | ||
== Unlock screensaver == <!--T:106--> | |||
<!--T:108--> | |||
If your VNC screensaver times out and requests a password, enter your cluster account password to unlock it (not your vncserver password). If you are running the MATE desktop and the screen saver will not unlock try running <code>killall -9 .mate-screensaver</code>. This should no longer be a problem on Compute Canada clusters as the VNC screen saver has been disabled. | |||
= Software = <!--T:104--> | = Software = <!--T:104--> | ||