--- old/Xvnc.txt 2009-10-30 13:24:16.285756953 -0700 +++ tigervnc-1.0/Xvnc.txt 2009-10-30 13:22:01.607660100 -0700 @@ -9,7 +9,7 @@ Xvnc - the X VNC server SYNOPSIS - Xvnc [options] :display# + /usr/X11/bin/Xvnc [options] :display# DESCRIPTION Xvnc is the X VNC (Virtual Network Computing) server. It is @@ -48,8 +48,8 @@ -depth depth Specify the pixel depth in bits of the desktop to be - created. Default is 16, other possible values are 8, - 15, and 24 - anything else is likely to cause strange + created. Default is 24, other possible values are 8, + 15, and 16 - anything else is likely to cause strange behaviour by applications. @@ -60,7 +60,7 @@ -RealVNC Ltd Last change: 03 Mar 2005 1 +TigerVNC Last change: 17 Apr 2006 1 @@ -79,7 +79,7 @@ -cc 3 As an alternative to the default TrueColor visual, this allows you to run an Xvnc server with a PseudoColor - visual (i.e. one which uses a colour map or palette), + visual (i.e. one which uses a color map or palette), which can be useful for running some old X applications which only work on such a display. Values other than 3 (PseudoColor) and 4 (TrueColor) for the -cc option may @@ -99,7 +99,8 @@ PARAMETERS VNC parameters can be set both via the command-line and - through the vncconfig(1) program. + through the vncconfig(1) program, and with a VNC-enabled + Xorg server via Options entries in the xorg.conf(4) file. Parameters can be turned on with -param or off with -param=0. Parameters which take a value can be specified as @@ -122,11 +123,10 @@ -rfbwait time, -ClientWaitTimeMillis time - Time in milliseconds to wait for a viewer which is -RealVNC Ltd Last change: 03 Mar 2005 2 +TigerVNC Last change: 17 Apr 2006 2 @@ -137,6 +137,7 @@ + Time in milliseconds to wait for a viewer which is blocking Xvnc. This is necessary because Xvnc is single-threaded and sometimes blocks until the viewer has finished sending or receiving a message - note that @@ -169,7 +170,7 @@ Xvnc uses a "deferred update" mechanism which enhances performance in many cases. After any change to the framebuffer, Xvnc waits for this number of milliseconds - (default 40) before sending an update to any waiting + (default 1) before sending an update to any waiting clients. This means that more changes tend to get coalesced together in a single update. Setting it to 0 results in the same behaviour as earlier versions of @@ -191,8 +192,7 @@ - -RealVNC Ltd Last change: 03 Mar 2005 3 +TigerVNC Last change: 17 Apr 2006 3 @@ -252,13 +252,13 @@ -IdleTimeout seconds The number of seconds after which an idle VNC connec- - tion will be dropped (default is 3600 i.e. an hour). - + tion will be dropped (default is 0, which means that + idle connections will never be dropped). -RealVNC Ltd Last change: 03 Mar 2005 4 +TigerVNC Last change: 17 Apr 2006 4 @@ -324,7 +324,7 @@ -RealVNC Ltd Last change: 03 Mar 2005 5 +TigerVNC Last change: 17 Apr 2006 5 @@ -356,10 +356,9 @@ Xvnc for that connection which should display the standard graphical login screen on that machine. (To enable this, you will also have to enable XDMCP network connections on - the login screen. See dtlogin(1) or gdm(1) for details.) - Because the user needs to login via this screen, it is usu- - ally OK to accept connections without a VNC password in this - case. + the login screen. See gdm(1) for details.) Because the + user needs to login via this screen, it is usually OK to + accept connections without a VNC password in this case. In the wait mode, when the first connection comes in, inetd gives the listening socket to Xvnc. This means that for a @@ -390,7 +389,8 @@ -RealVNC Ltd Last change: 03 Mar 2005 6 + +TigerVNC Last change: 17 Apr 2006 6 @@ -404,30 +404,30 @@ SEE ALSO vncconfig(1), vncpasswd(1), vncserver(1), vncviewer(1), Xserver(1), inetd(1) - http://www.realvnc.com + http://www.tigervnc.org AUTHOR Tristan Richardson, RealVNC Ltd. VNC was originally developed by the RealVNC team while at - Olivetti Research Ltd / AT&T Laboratories Cambridge. It is - now being maintained by RealVNC Ltd. See - http://www.realvnc.com for details. - - - - - - - - - - - + Olivetti Research Ltd / AT&T Laboratories Cambridge. + TightVNC additions were implemented by Constantin Kaplinsky. + Many other people participated in development, testing and + support. +ATTRIBUTES + See attributes(5) for descriptions of the following attri- + butes: + ____________________________________________________________ + | ATTRIBUTE TYPE | ATTRIBUTE VALUE | + |_____________________________|_____________________________| + | Availability | SUNWxvnc | + |_____________________________|_____________________________| + | Interface Stability | Volatile | + |_____________________________|_____________________________| @@ -456,7 +456,7 @@ -RealVNC Ltd Last change: 03 Mar 2005 7 +TigerVNC Last change: 17 Apr 2006 7