VNC: Difference between revisions

VNC (view source)

Revision as of 00:37, 4 September 2024

112 bytes added , 2 months ago

m

no edit summary

Roberpj

cc_staff

1,857

edits

@@ Line 93: / Line 93: @@
 <!--T:44-->
-) 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 changed later as described below.  The password will insure only you can establish multiple connections (as described below) if you started the vncserver with the optional <code>-alwaysshared</code> option shown here in square brackets:
+) 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 changed later as described below.  The password will insure only you can establish multiple connections to your desktop as described in section [https://docs.alliancecan.ca/wiki/VNC#Multiple_connections | 3.3] assuming you originally started your vncserver with the optional <code>-alwaysshared</code> argument option shown here in square brackets:
 <!--T:164-->