Thread safety. Fix -clip -in -rawfb. Try to avoid Xorg stuck

key bug.

1 files changed, 30 insertions, 11 deletions

diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1
index 8b54664..fcb499b 100644
--- a/x11vnc/x11vnc.1
+++ b/x11vnc/x11vnc.1
@@ -1,8 +1,8 @@
 .\" This file was automatically generated from x11vnc -help output.
-.TH X11VNC "1" "March 2009" "x11vnc " "User Commands"
+.TH X11VNC "1" "May 2009" "x11vnc " "User Commands"
 .SH NAME
 x11vnc - allow VNC connections to real X11 displays
-         version: 0.9.8, lastmod: 2009-03-30
+         version: 0.9.8, lastmod: 2009-05-18
 .SH SYNOPSIS
 .B x11vnc
 [OPTION]...
@@ -1003,6 +1003,9 @@ associated with it does apply as normal.
 There are also some utilities for testing password
 if [list] starts with the "%" character.  See the
 quick_pw() function in the source for details.
+.IP
+Use \fB-nounixpw\fR to disable unixpw mode if it was enabled
+earlier in the cmd line (e.g. \fB-svc\fR mode)
 .PP
 \fB-unixpw_nis\fR \fI[list]\fR
 .IP
@@ -3114,10 +3117,13 @@ Option \fB-norepeat\fR disables X server key auto repeat when
 VNC clients are connected and VNC keyboard input is
 not idle for more than 5 minutes.  This works around a
 repeating keystrokes bug (triggered by long processing
-delays between key down and key up client events: either
-from large screen changes or high latency).
+delays between key down and key up client events:
+either from large screen changes or high latency).
 Default: \fB-norepeat\fR
 .IP
+You can set the env. var. X11VNC_IDLE_TIMEOUT to the
+number of idle seconds you want (5min = 300secs).
+.IP
 Note: your VNC viewer side will likely do autorepeating,
 so this is no loss unless someone is simultaneously at
 the real X display.
@@ -3667,7 +3673,7 @@ If a pattern is prefixed with "KEY:" it only applies
 to Keystroke generated scrolls (e.g. Up arrow).  If it
 is prefixed with "MOUSE:" it only applies to Mouse
 induced scrolls (e.g. dragging on a scrollbar).
-Default: ##Soffice.bin,##StarOffice
+Default: ##Soffice.bin,##StarOffice,##OpenOffice
 .PP
 \fB-scr_inc\fR \fIlist\fR
 .IP
@@ -4211,12 +4217,25 @@ for this option if you don't like the 'pipe'. Example:
 \fB-threads,\fR \fB-nothreads\fR
 .IP
 Whether or not to use the threaded libvncserver
-algorithm [rfbRunEventLoop] if libpthread is available
-Default: \fB-nothreads.\fR  NOTE:  The \fB-threads\fR mode is now
-disabled due to its unstable behavior.  Not recommended,
-but you can recompile with \fB-DX11VNC_THREADED\fR in
-CPPFLAGS if you need to use it.  You can also set the
-env. variable X11VNC_THREADED=1
+algorithm [rfbRunEventLoop] if libpthread is available.
+In this mode new threads (one for input and one
+for output) are created to handle each new client.
+Default: \fB-nothreads.\fR
+.IP
+NOTE:  The \fB-threads\fR mode may be disabled due to its
+unstable behavior.  If it is disabled, a warning is
+printed out.  Stability has been improved in version
+0.9.8 and so the feature has been re-enabled.
+.IP
+Multiple clients in threaded mode should be stable
+for the ZRLE encoding on all platforms.  The Tight and
+Zlib encodings are currently only stable on Linux for
+multiple clients.  Compile with \fB-DTLS=__thread\fR if your
+OS and compiler and linker support it.
+.IP
+Multiple clients in threaded mode could yield better
+performance for 'class-room' broadcasting usage.
+See also the \fB-reflect\fR option.
 .PP
 \fB-fs\fR \fIf\fR
 .IP