VNC: Difference between revisions

Jump to navigation Jump to search
176 bytes added ,  2 months ago
m
no edit summary
mNo edit summary
mNo edit summary
Line 93: Line 93:


<!--T:44-->
<!--T:44-->
1) Since moving to turbovnc on the clusters, the previously documented MaxConnectionTime of 1hr (3600 sec) is no longer supported.  Instead we suggest you set an idle timeout value to something like 7days before your session is killed.  This way unused sessions consuming vital memory resources will not accumulate on cluster login nodes over time.  The first time you connect, vncserver will require a password be set which can be [https://docs.alliancecan.ca/wiki/VNC#Vncserver_password changed] later.  The password insure only you can establish [https://docs.alliancecan.ca/wiki/VNC#Multiple_connections multiple connections] to your desktop(s). This functionality requires you originally started your vncserver with the optional <code>-alwaysshared</code> option shown here:
1) Since moving to [https://turbovnc.org turbovnc] on the clusters, the previously recommended <code>-maxconnectiontime</code> vncserver option is no longer supported.  Instead use <code>vncserver -idletimeout seconds</code> to ensure your session is eventually killed.  This will ensure any unnecessarily consumed system resources associated with your desktop (such as memory) will be released.  The first time you start vncserver you will be required to set a password which can be [https://docs.alliancecan.ca/wiki/VNC#Vncserver_password changed] later.  The password will be required to remotely connect to your desktop with a vncclient (such as vncviewer).  Likewise the password will be required when making [https://docs.alliancecan.ca/wiki/VNC#Multiple_connections multiple connections] assuming you started vncserver with the additional <code>-alwaysshared</code> option shown here (the square brackets mean optional and should not be included):


<!--T:164-->
<!--T:164-->
cc_staff
1,857

edits

Navigation menu