Changes between Version 2 and Version 3 of vnc3d/vglconnect
- Timestamp:
- 09/30/16 09:58:27 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
vnc3d/vglconnect
v2 v3 31 31 \\ 32 32 === 2. Start an X Server ... 33 Start an X Server on your local machine. 34 * Linux - your X11 server is used for your standard desktop and should be running already 35 * MacOSX - start the Mac X11 application \\ in the X11 application, start a new xterm [Command-N] if one isn’t already started 36 * Windows\Cygwin - start Cygwin/X \\ start a new xterm if one isn’t already started (right-click on the Cygwin/X taskbar icon, then select Applications–>xterm.) 37 38 \\ 39 === 3. Connect to JURECAVIS ... 33 40 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. 34 41 By default the X11 traffic is encrypted, but the VGL Transport is left unencrypted to maximize performance. 35 42 This will fail on JURECA - you need to encrypt the VGL Transport, too, which is forced with the '''-s''' flag: 36 43 44 {{{ #!sh 45 vglconnect -s <USERID>@jurecavis.fz-juelich.de 46 }}} 37 47 48 === 4. Start the application ... 49 {{{ #!sh 50 vglrun <APP> 51 }}} 38 52 39 40 41 Start an X Server on your local machine. 42 43 === 3. Connct to JURECAVIS ... 44 45 The X11 traffic is encrypted, but the VGL Transport is left unencrypted to maximize performance. 46 You can start the VNC server ... 47 * ... on an '''interactive vis login node''' 48 * + no batch system == instant access 49 * -- system is shared with other users 50 * ... on a '''dedicated vis node''' 51 * + system is not shared (exclusive use) 52 * -- access through batch system 53 [http://www.virtualgl.org/vgldoc/2_2/#hd007 | more ...]
