FarmVNC

From FarmShare

(Difference between revisions)
Jump to: navigation, search
m
 
(17 intermediate revisions not shown)
Line 1: Line 1:
-
== FarmVNC ==
+
The FarmVNC script has been retired. VNC remote display is still supported, but X Windows is strongly recommended, instead; see the [https://srcc.stanford.edu/farmshare2/connecting service documentation] for instructions.
-
 
+
-
This page documents a new script - farmvnc - which has been introduced with the upgrade to Ubuntu 13.04.  The steps involved in setting up VNC on Farmshare are largely the same as the previous VNC instructions, but with substitution of farmvnc script instead of vncserver.
+
-
 
+
-
== first steps ==
+
-
* check that you have your AFS tokens or else things will fail because they can't write to your homedir
+
-
  kinit && aklog
+
-
* set your vnc password if you haven't already
+
-
  vncpasswd
+
-
 
+
-
This VNC password is for the VNC connections only.  It's stored in a file in your homedir so it's best to use a different password for this.  Don't use your SUNetID password.
+
-
 
+
-
== running farmvnc ==
+
-
 
+
-
First, run farmvnc to see what resolutions are supported:
+
-
 
+
-
<source lang="sh">
+
-
$ module load farmvnc
+
-
$ farmvnc
+
-
please give desired resolution on command line:
+
-
for example: farmvnc 1440x900
+
-
 
+
-
you can choose any of the following
+
-
1024x768
+
-
1280x1024
+
-
1440x900
+
-
1920x1080
+
-
1920x1000
+
-
 
+
-
</source>
+
-
 
+
-
I am using a macbook air 13" so I will choose 1440x900 so that full screen vnc will match with native mac resolution.
+
-
 
+
-
<source lang="sh">
+
-
$ module load farmvnc
+
-
$ farmvnc 1440x900
+
-
using display 1
+
-
Initializing built-in extension Generic Event Extension
+
-
Initializing built-in extension SHAPE
+
-
Initializing built-in extension MIT-SHM
+
-
Initializing built-in extension XInputExtension
+
-
Initializing built-in extension XTEST
+
-
Initializing built-in extension BIG-REQUESTS
+
-
Initializing built-in extension SYNC
+
-
Initializing built-in extension XKEYBOARD
+
-
Initializing built-in extension XC-MISC
+
-
Initializing built-in extension SECURITY
+
-
Initializing built-in extension XINERAMA
+
-
Initializing built-in extension XFIXES
+
-
Initializing built-in extension RENDER
+
-
Initializing built-in extension RANDR
+
-
Initializing built-in extension COMPOSITE
+
-
Initializing built-in extension DAMAGE
+
-
Initializing built-in extension MIT-SCREEN-SAVER
+
-
Initializing built-in extension DOUBLE-BUFFER
+
-
Initializing built-in extension RECORD
+
-
Initializing built-in extension DPMS
+
-
Initializing built-in extension X-Resource
+
-
Initializing built-in extension XVideo
+
-
Initializing built-in extension XVideo-MotionCompensation
+
-
Initializing built-in extension SELinux
+
-
Initializing built-in extension XFree86-VidModeExtension
+
-
Initializing built-in extension XFree86-DGA
+
-
Initializing built-in extension XFree86-DRI
+
-
Initializing built-in extension DRI2
+
-
Loading extension GLX
+
-
 
+
-
 
+
-
###
+
-
##
+
-
# Mac and Linux users
+
-
# run this command in another window to setup the SSH tunnel
+
-
#
+
-
# ssh -L 5901:localhost:5911 bishopj@corn12.stanford.edu
+
-
#
+
-
# Windows users
+
-
# use these values in SS-VNC
+
-
#
+
-
# VNC Host Display: localhost:11
+
-
# Proxy/Gateway:    bishopj@corn12.stanford.edu
+
-
##
+
-
###
+
-
 
+
-
 
+
-
The VNC desktop is:      localhost:11
+
-
PORT=5911
+
-
 
+
-
</source>
+
-
 
+
-
At this point the VNC server is running on a specific corn.  The next step is to set up an SSH tunnel so that the vnc client that we need to run on your desktop/laptop can connect to the vncserver.
+
-
 
+
-
If you are running linux or macos on your laptop/desktop I would suggest cutting and pasting the ssh command that is displayed in the output of farmvnc into a new terminal window.  For example I would run this command (keep in mind that the username and port numbers will change from what is written here).
+
-
 
+
-
Linux/Mac:
+
-
 
+
-
<source lang="sh">
+
-
ssh -L 5901:localhost:5911 bishopj@corn12.stanford.edu
+
-
</source>
+
-
 
+
-
 
+
-
Windows:
+
-
 
+
-
For windows, cut and paste the SS-VNC config from above into the appropriate spots
+
-
 
+
-
<source lang="sh">
+
-
VNC Host Display: localhost:11
+
-
Proxy/Gateway:    bishopj@corn12.stanford.edu
+
-
</source>
+
-
 
+
-
 
+
-
== choice of vnc client ==
+
-
 
+
-
 
+
-
Ubuntu 13.04 desktop makes use of 3D effects.  You can turn some of these effects off, however, you are going to want a reasonably good VNC client.  I would suggest turboVNC if it is available to you.  For Windows, setting up the ssh tunnel for TurboVNC perhaps makes it not worth the trouble.  For Windows, SS-VNC does it tunnel for you so for the moment we recommend using it instead of TurboVNC.
+
-
 
+
-
[[Image:runturbovnc1.png|frame]]
+
-
[[Image:runsshvnc1.png|frame]]
+
-
 
+
-
 
+
-
You can get turboVNC from: http://sourceforge.net/projects/turbovnc/files/
+
-
 
+
-
You can get SS-VNC from: http://sourceforge.net/projects/ssvnc
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
[[Image:runturbovnc2.png|frame]]
+
-
 
+
-
 
+
-
[[Image:runturbovnc3.png|frame]]
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
MAC: Launch turbovnc and type in localhost:5901
+
-
 
+
-
Linux: /opt/TurboVNC/bin/vncviewer -highqual -encodings "tight copyrect" localhost:5901
+
-
 
+
-
Windows: launch SS-VNC and enter settings
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
Type in your vnc password that you set in previous step.
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
You should see an Ubuntu desktop environment that looks something like this
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
== reconnecting vnc client ==
+
-
 
+
-
If you login to FarmShare again, you can discover your vnc sessions by running listfarmvncsessions as in:
+
-
 
+
-
<source lang="sh">
+
-
$ module load farmvnc
+
-
$ listfarmvncsessions
+
-
active vnc session:
+
-
  TurboVNC
+
-
    ssh -L 5901:localhost:5911 bishopj@corn12.stanford.edu
+
-
 
+
-
  SS-VNC
+
-
    Vnc Host:Display    localhost:11
+
-
    Proxy/Gateway      bishopj@corn12.stanford.edu
+
-
 
+
-
</source>
+
-
 
+
-
 
+
-
== Logging out ==
+
-
 
+
-
[[Image:turbovnclogout1.png|frame]]
+
-
 
+
-
 
+
-
 
+
-
When you are done with your VNC session and you want to shut everything down.  Select Logout from the menu in upper right of your screen.
+
-
 
+
-
[[Image:turbovnclogout2.png|frame]]
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
[[Image:turbovnclogout3.png|frame]]
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
Wait for a few seconds while the logout screen fades in (takes around 5-10 seconds)
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
Click the logout icon and you should see turboVNC say closed connection.
+
-
 
+
-
 
+
-
 
+
-
 
+
-
Another way you can "log out" is by simply killing all your processes on that corn machine.  E.g. log in to that corn and say "kill all processes owned by me":
+
-
  ssh cornXX
+
-
  kill -1 -1
+
-
 
+
-
That will kill all your processes on that machine including your SSH connection, so you'll get disconnected immediately.
+
-
 
+
-
==older instructions==
+
-
If you have any trouble with the above, try the older instructions:
+
-
*https://itservices.stanford.edu/service/sharedcomputing/vnc
+
-
 
+
-
==other instructions==
+
-
http://web.stanford.edu/class/cs107/other/x_tutorial/
+

Latest revision as of 09:41, 27 June 2019

The FarmVNC script has been retired. VNC remote display is still supported, but X Windows is strongly recommended, instead; see the service documentation for instructions.

Personal tools
Toolbox
LANGUAGES