cc_staff
1,857
edits
VNC: Difference between revisions
Jump to navigation
Jump to search
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 changed later as described below. The password will insure only you can establish multiple connections | 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 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--> | <!--T:164--> | ||