VNC: Difference between revisions

Jump to navigation Jump to search
136 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 specified which can be changed later as described below.
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 (as described below) if you started the vncserver with the optional <code>-alwaysshared</code> option shown here in square brackets:


<!--T:164-->
<!--T:164-->
  [<b>gra-login2</b>:~] vncserver -idletimeout 604800
  [<b>gra-login2</b>:~] vncserver -idletimeout 604800 [-alwaysshared]
You will require a password to access your desktops.
Password:
Verify: 
  Would you like to enter a view-only password (y/n)? n
  Would you like to enter a view-only password (y/n)? n
  Desktop 'TurboVNC: gra-login2:2 (username)' started on display gra-login2:2
  Desktop 'TurboVNC: gra-login2:2 (username)' started on display gra-login2:2
cc_staff
1,857

edits

Navigation menu