Changes between Version 12 and Version 13 of vnc3d/vglconnect

Timestamp:

10/03/16 12:42:26 (8 years ago)

Author:

Jens Henrik Goebbert

Comment:

--

vnc3d/vglconnect

@@ -1 @@
-== Using VirtualGL with the VGL Transport
+== Using VirtualGL with the VGL Transport (and no VNC)
 [[PageOutline]]
 
@@ -55 +55 @@
 \\
 === 3. Connect to JURECAVIS ...
-In this scenario any OpenGL commands are computed to a JPEG on JURECAVIS and send to the local machine via the VGL Transport Layer. The 2D (X11) command are directly passed to the local X server running on your machine.
-By default the X11 traffic is encrypted, but the VGL Transport is left unencrypted to maximize performance.
-This will fail on JURECA - you need to encrypt the VGL Transport, too, which is forced with the '''-s''' flag:
+In this scenario any OpenGL commands are computed to a JPEG on JURECAVIS and send to the local machine via the VGL Transport Layer.\\
+The 2D (X11) command are directly passed to the local X server running on your machine.
+
+By default the X11 traffic is encrypted, but the VGL Transport is left unencrypted to maximize performance.\\
+This will fail on JURECA - you '''need to encrypt''' the VGL Transport, too, which is forced with the '''-s''' flag:
 
 {{{ #!sh
@@ -66 +68 @@
 
 '''Important:''' \\
-vglconnect searches for additional VirtualGL-tools in $VGL_BINDIR on your local machine if set - elsewise it expects these in /usr/bin.
+vglconnect searches for additional VirtualGL-tools in $VGL_BINDIR on your local machine if set.\\
+Elsewise it expects these at a default location which can differ depending on your installation.\\
+(/usr/bin or /opt/VirtualGL/bin - check vglconnect script to know)
 
 [http://www.virtualgl.org/vgldoc/2_2/#hd007006 | more ...]
 
 === 4. Start the application ...
-Now start your application on JURECA with '''vglrun''':
+Now you are logged in to JURECA and must start your OpenGL application on JURECA with '''vglrun''':
 {{{ #!sh
 vglrun <APP>