summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorrunge <runge>2005-05-31 03:26:04 +0000
committerrunge <runge>2005-05-31 03:26:04 +0000
commit4effb62e99925e19f2b4b14041d57574f3763f23 (patch)
tree184574c05c1fe806fd5ada6252501bdf92a3be63
parent813f4211ee483f2e6ef32265970cfe4d67b84491 (diff)
downloadlibtdevnc-4effb62e.tar.gz
libtdevnc-4effb62e.zip
main.c: fix copyRect for non-cursor-shape-aware clients.
Diffstat
-rw-r--r--ChangeLog3
-rw-r--r--libvncserver/main.c43
-rw-r--r--x11vnc/ChangeLog4
-rw-r--r--x11vnc/README866
-rw-r--r--x11vnc/x11vnc.122
-rw-r--r--x11vnc/x11vnc.c74
6 files changed, 568 insertions, 444 deletions
diff --git a/ChangeLog b/ChangeLog
index 0e0f0a4..9e829ac 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,6 @@
+2005-05-30 Karl Runge <runge@karlrunge.com>
+ * libvncserver/main.c: fix copyRect for non-cursor-shape-aware clients.
+
2005-05-24 Karl Runge <runge@karlrunge.com>
* x11vnc: scrollcopyrect: GrabServer detection, autorepeat throttling..
* prepare_x11vnc_dist.sh: grep out new libvncserver-config line.
diff --git a/libvncserver/main.c b/libvncserver/main.c
index bf1f211..e4d1ea7 100644
--- a/libvncserver/main.c
+++ b/libvncserver/main.c
@@ -130,6 +130,49 @@ void rfbScheduleCopyRegion(rfbScreenInfoPtr rfbScreen,sraRegionPtr copyRegion,in
sraRgnAnd(modifiedRegionBackup,cl->copyRegion);
sraRgnOr(cl->modifiedRegion,modifiedRegionBackup);
sraRgnDestroy(modifiedRegionBackup);
+
+ if(!cl->enableCursorShapeUpdates) {
+ /*
+ * n.b. (dx, dy) is the vector pointing in the direction the
+ * copyrect displacement will take place. copyRegion is the
+ * destination rectangle (say), not the source rectangle.
+ */
+ sraRegionPtr cursorRegion;
+ int x = cl->cursorX - cl->screen->cursor->xhot;
+ int y = cl->cursorY - cl->screen->cursor->yhot;
+ int w = cl->screen->cursor->width;
+ int h = cl->screen->cursor->height;
+
+ cursorRegion = sraRgnCreateRect(x, y, x + w, y + h);
+ sraRgnAnd(cursorRegion, cl->copyRegion);
+ if(!sraRgnEmpty(cursorRegion)) {
+ /*
+ * current cursor rect overlaps with the copy region *dest*,
+ * so remove it from the copy-rect treatment, and mark it as
+ * modified since we won't copy-rect stuff to it.
+ */
+ sraRgnSubtract(cl->copyRegion, cursorRegion);
+ sraRgnOr(cl->modifiedRegion, cursorRegion);
+ }
+ sraRgnDestroy(cursorRegion);
+
+ cursorRegion = sraRgnCreateRect(x, y, x + w, y + h);
+ /* displace it to check for overlap with copy region source: */
+ sraRgnOffset(cursorRegion, dx, dy);
+ sraRgnAnd(cursorRegion, cl->copyRegion);
+ if(!sraRgnEmpty(cursorRegion)) {
+ /*
+ * current cursor rect overlaps with the copy region *source*,
+ * so remove it from the copy-rect treatment, and mark the
+ * *displaced* cursorRegion as modified since we won't copyrect
+ * stuff to it.
+ */
+ sraRgnSubtract(cl->copyRegion, cursorRegion);
+ sraRgnOr(cl->modifiedRegion, cursorRegion);
+ }
+ sraRgnDestroy(cursorRegion);
+ }
+
} else {
sraRgnOr(cl->modifiedRegion,copyRegion);
}
diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog
index 964f754..b3a0ce1 100644
--- a/x11vnc/ChangeLog
+++ b/x11vnc/ChangeLog
@@ -1,3 +1,7 @@
+2005-05-30 Karl Runge <runge@karlrunge.com>
+ * alter "magic cleanup key sequences" (N*Alt_L and N*Super_L)
+ * dial down check_xrecord_reset() reset times.
+
2005-05-24 Karl Runge <runge@karlrunge.com>
* more -scrollcopyrect: GrabServer detection, autorepeat throttling,
hack to clean screen 3,4,5 Alt_L in a row, mouse wheel detect.
diff --git a/x11vnc/README b/x11vnc/README
index 8b9f1c1..4666090 100644
--- a/x11vnc/README
+++ b/x11vnc/README
@@ -1,5 +1,5 @@
-x11vnc README file Date: Tue May 24 23:49:07 EDT 2005
+x11vnc README file Date: Tue May 31 00:10:51 EDT 2005
The following information is taken from these URLs:
@@ -309,20 +309,16 @@ vncviewer -via $host localhost:0 # must be TightVNC vncviewer.
The x11vnc package is the subset of the libvncserver package needed to
build the x11vnc program. Also, you can get a copy of my latest,
- bleeding edge [37]x11vnc.c file to replace the one in the above
- packages or the one in the CVS tree and then rebuild. You can also
- update the tcl/tk gui with the [38]tkx11vnc.h file. If you have an
- older libvncserver source tree, you may need to switch on the OLD_TREE
- variable near the top of the x11vnc.c file.
+ bleeding edge [37]x11vnc-0.7.2.tar.gz tarball.
- See the [39]FAQ below for information about where you might obtain a
+ See the [38]FAQ below for information about where you might obtain a
precompiled x11vnc binary from 3rd parties.
To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix)
try these links:
- * [40]http://www.tightvnc.com/download.html
- * [41]http://www.realvnc.com/download-free.html
- * [42]http://sourceforge.net/projects/cotvnc/
+ * [39]http://www.tightvnc.com/download.html
+ * [40]http://www.realvnc.com/download-free.html
+ * [41]http://sourceforge.net/projects/cotvnc/
More tools: Here is a rsh/ssh wrapper script rx11vnc that attempts to
@@ -333,8 +329,8 @@ vncviewer -via $host localhost:0 # must be TightVNC vncviewer.
rx11vnc.pl that attempts to tunnel the vnc traffic through an ssh port
redirection (and does not assume port 5900 is free). Have a look at
them to see what they do and customize as needed:
- * [43]rx11vnc wrapper script
- * [44]rx11vnc.pl wrapper script to tunnel traffic thru ssh
+ * [42]rx11vnc wrapper script
+ * [43]rx11vnc.pl wrapper script to tunnel traffic thru ssh
_________________________________________________________________
@@ -364,11 +360,37 @@ vncviewer -via $host localhost:0 # must be TightVNC vncviewer.
Note: Currently gcc is required to build libvncserver. In some cases
it will build with non-gcc compilers, but the resulting binary often
fails to run properly. For Solaris pre-built gcc binaries are at
- [45]http://www.sunfreeware.com/ However, one user reports it does
+ [44]http://www.sunfreeware.com/ However, one user reports it does
work fine when built with Sun Studio 10, so YMMV.
_________________________________________________________________
+ Misc. Build problems: We collect here rare build problems some users
+ have reported and the corresponding workarounds. See also the
+ [45]FAQ's on building.
+
+ One user had a problem where the build script below was failing
+ because his work environment had the ENV variable set to a script that
+ was resetting his PATH so that gcc could no longer be found. Make sure
+ you do not have any ENV or BASH_ENV in your environment doing things
+ like that. Typing "unset ENV", etc. before configuring and building
+ should clear it.
+
+ One user had his bash shell compiled with --enable-xpg-echo-default
+ that causes some strange behavior with things like echo "\\1 ..." the
+ configure script executes. In particular instead of getting "\1" the
+ non-printable character "^A" is produced, and causes failures at
+ compile time like:
+ ../rfb/rfbconfig.h:9:22: warning: extra tokens at end of #ifndef directive
+
+ The workaround is to configure like this:
+ env CONFIG_SHELL=/bin/sh /bin/sh ./configure
+
+ i.e. avoid using the bash with the misbehavior. A bug has been filed
+ against autoconf to guard against this.
+
+ _________________________________________________________________
+
Building on Solaris, FreeBSD, etc: Depending on your version of
Solaris or other Unix OS the jpeg and/or zlib libraries may be in
non-standard places (e.g. /usr/local, /usr/sfw, /opt/sfw, etc).
@@ -473,12 +495,6 @@ ls -l ./x11vnc/x11vnc
--with-zlib=DIR" options are handy if you want to avoid making a
script.
- One user had a problem where the above build script was failing
- because his work environment had the ENV variable set to a script that
- was resetting his PATH so that gcc could no longer be found. Make sure
- you do not have any ENV or BASH_ENV in your environment doing things
- like that.
-
If you need to build on Solaris 2.5.1 or earlier or other older Unix
OS's, see [49]this workaround FAQ.
@@ -521,7 +537,7 @@ make
I don't have any formal beta-testers for the releases of x11vnc, so
I'd appreciate any additional testing very much!
- I'd like to release version 0.7.2 in Apr/May 2005 sometime, here is
+ I'd like to release version 0.7.2 in May/Jun 2005 sometime, here is
the current tarball: [50]x11vnc-0.7.2.tar.gz. Please kick the tires,
and report bugs, performance regressions, etc. to [51]me.
@@ -1346,9 +1362,8 @@ display :0
the next I/O operation and will close the connection and continue on.
Up until of Apr/2004 the above fix only works for BSD signal systems
- (Linux, FreeBSD, ...) For SYSV systems there is a workaround in my
- [171]x11vnc.c file. It also has an [172]option -sigpipe exit to have
- x11vnc clean up and exit upon receiving SIGPIPE.
+ (Linux, FreeBSD, ...) For SYSV systems there is a workaround in place
+ since about Jun/2004.
Q-11: Are there any build-time customizations possible, e.g. change
@@ -1356,7 +1371,7 @@ display :0
As of Mar/2004 in the libvncserver cvs there are a few such options.
They are enabled by adding something like -Dxxxx=1 to the CPPFLAGS
- environment variable before running configure (see the [173]build
+ environment variable before running configure (see the [171]build
notes for general background).
* -DX11VNC_SHARED=1 make -shared the default.
* -DX11VNC_FOREVER=1 make -forever the default.
@@ -1403,21 +1418,21 @@ display :0
dual-screen mode to pass the keystrokes and mouse motions to the X11
display?
- Yes, for best response start up x11vnc with the "[174]-nofb" option
+ Yes, for best response start up x11vnc with the "[172]-nofb" option
(disables framebuffer polling, and does other optimizations) on the
secondary display (X11) machine. Then start up Win2VNC on the primary
display (Windows) referring it to the secondary display.
- This will also work X11 to X11 using [175]x2vnc, however you would
+ This will also work X11 to X11 using [173]x2vnc, however you would
probably just want to avoid VNC and use x2x for that.
For reference, here are some links to Win2VNC-like programs for
multiple monitor setups:
- * [176]Original Win2VNC
- * [177]Enhanced Win2VNC and [178]sourceforge link
- * [179]x2vnc
- * [180]x2x also [181]here
- * [182]zvnc (MorphOS)
+ * [174]Original Win2VNC
+ * [175]Enhanced Win2VNC and [176]sourceforge link
+ * [177]x2vnc
+ * [178]x2x also [179]here
+ * [180]zvnc (MorphOS)
All of them will work with x11vnc (except x2x where it is not needed).
@@ -1437,7 +1452,7 @@ display :0
on your display to be depth 24 TrueColor? Sun machines often have 8+24
overlay/multi-depth visuals, and you can make the default visual depth
24 TrueColor (see fbconfig(1) and Xsun(1)). 2) As of Feb/2004, in the
- libvncserver CVS, x11vnc has the [183]-visual option to allow you to
+ libvncserver CVS, x11vnc has the [181]-visual option to allow you to
force the framebuffer visual to whatever you want (this usually messes
up the colors unless you are very clever). In this case, the option
provides a convenient workaround for the Win2VNC bug:
@@ -1452,7 +1467,7 @@ display :0
PseudoColor (i.e. only 256 distinct colors). The x11vnc colors may
start out OK, but after a while they are incorrect in certain windows.
- Use the [184]-flashcmap option to have x11vnc watch for changes in the
+ Use the [182]-flashcmap option to have x11vnc watch for changes in the
colormap, and propagate those changes back to connected clients. This
can be slow (since the whole screen must be updated over the network
whenever the colormap changes). This flashing colormap behavior often
@@ -1461,7 +1476,7 @@ display :0
example of this. Consider reconfiguring the system to 16 bpp or depth
24 TrueColor if at all possible.
- Also note that in some rare cases the [185]-notruecolor option has
+ Also note that in some rare cases the [183]-notruecolor option has
corrected colors on 8bpp displays. The red, green, and blue masks were
non-zero in 8bpp PseudoColor on an obscure setup, and this option
corrected the problems.
@@ -1472,10 +1487,10 @@ display :0
different color depths: e.g. there are both depth 8 and 24 visuals
available at the same time.
- You may want to review the [186]previous question regarding 8 bpp
+ You may want to review the [184]previous question regarding 8 bpp
PseudoColor.
- On some hardware (Sun/SPARC, Sgi), the [187]-overlay option discussed
+ On some hardware (Sun/SPARC, Sgi), the [185]-overlay option discussed
a couple paragraphs down may solve this for you (you may want to skip
to it directly).
@@ -1513,7 +1528,7 @@ TrueColor defdepth 24
The -overlay mode: Another option is if the system with overlay
visuals is a Sun system running Solaris or Sgi running IRIX you can
- use the [188]-overlay x11vnc option (Aug/2004) to have x11vnc use the
+ use the [186]-overlay x11vnc option (Aug/2004) to have x11vnc use the
Solaris XReadScreen(3X11) function to poll the "true view" of the
whole screen at depth 24 TrueColor. XReadDisplay(3X11) is used on
IRIX. This is useful for Legacy applications (older versions of
@@ -1535,7 +1550,7 @@ TrueColor defdepth 24
Colors still not working correctly? Run xwininfo on the application
with the messed up colors to verify that the depth of its visual is
different from the default visual depth (gotten from xdpyinfo). One
- possible workaround in this case is to use the [189]-id option to
+ possible workaround in this case is to use the [187]-id option to
point x11vnc at the application window itself. If the application is
complicated (lots of toplevel windows and popup menus) this may not be
acceptable, and may even crash x11vnc (but not the application).
@@ -1543,7 +1558,7 @@ TrueColor defdepth 24
It is theoretically possible to solve this problem in general (see
xwd(1) for example), but it does not seem trivial or sufficiently fast
for x11vnc to be able to do so in real time. Fortunately the
- [190]-overlay option works for Solaris machines with overlay visuals
+ [188]-overlay option works for Solaris machines with overlay visuals
where most of this problem occurs.
@@ -1554,13 +1569,13 @@ TrueColor defdepth 24
the desired application window. After clicking, it will print out much
information, including the window id (e.g. 0x6000010). Also, the
visual and depth of the window printed out is often useful in
- debugging x11vnc [191]problems.
+ debugging x11vnc [189]problems.
When using -id windowid, note that some VNC viewers will have problems
rendering screens that have a width that is not a multiple of 4. Try
to manually adjust the window width before starting x11vnc -id ....
- Also, as of Dec/2004 libvncserver CVS you can use "[192]-id pick" to
+ Also, as of Dec/2004 libvncserver CVS you can use "[190]-id pick" to
have x11vnc run xwininfo(1) for you and after you click the window it
extracts the windowid. Besides "pick" there is also "id:root" to allow
you to go back to root window when doing remote-control.
@@ -1578,7 +1593,7 @@ TrueColor defdepth 24
be able to see these transient windows.
If things are not working and you still want to do the single window
- polling, try the [193]-sid windowid option ("shifted" windowid).
+ polling, try the [191]-sid windowid option ("shifted" windowid).
x11vnc is known to crash under both -id and -sid, so both modes are
still experimental. Please report any reproducible bugs.
@@ -1631,15 +1646,15 @@ TrueColor defdepth 24
since you will be polling the X display over the network as opposed to
over the local hardware. To do this, run x11vnc on a UNIX machine as
close as possible network-wise (e.g. same switch) to the Xterminal
- machine. Use the [194]-display option to point the display to that of
+ machine. Use the [192]-display option to point the display to that of
the Xterminal (you'll of course need basic X11 permission to do that)
- and also supply the [195]-noshm option (this enables the polling over
+ and also supply the [193]-noshm option (this enables the polling over
the network).
The response will likely be sluggish (maybe only one "frame" per
second). This mode is not recommended except for "quick checks" of
hard to get to X servers. Use something like -wait 150 to cut down on
- the polling rate. You may also need [196]-flipbyteorder if the colors
+ the polling rate. You may also need [194]-flipbyteorder if the colors
get messed up due to endian byte order differences.
Q-20: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for a
@@ -1663,7 +1678,7 @@ TrueColor defdepth 24
copied to the Xterminal. If $HOME/.Xauthority is exported via NFS
(this is insecure of course, but has been going on for decades), then
x11vnc can simply pick it up via NFS (you may need to use the
- [197]-auth option to point to the correct file). Other options include
+ [195]-auth option to point to the correct file). Other options include
copying the auth file using scp, or something like:
central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
@@ -1675,7 +1690,7 @@ TrueColor defdepth 24
details.
If the display name in the cookie file needs to be changed between the
- two hosts, see [198]this note on the "xauth add ..." command.
+ two hosts, see [196]this note on the "xauth add ..." command.
A less secure option is to run something like "xhost +127.0.0.1" while
sitting at the Xterminal box to allow cookie-free local access for
@@ -1689,7 +1704,7 @@ TrueColor defdepth 24
occasional app more efficiently locally on the Xterminal box (e.g.
realplayer).
- Not recommended, but as a last resort, you could have x11vnc [199]poll
+ Not recommended, but as a last resort, you could have x11vnc [197]poll
the Xterminal Display over the network. For this you would run a
"x11vnc -noshm ..." process on the central-server (and hope the
network admin doesn't get angry...)
@@ -1720,17 +1735,17 @@ TrueColor defdepth 24
As of Dec/2004 in the libvncserver CVS there is a remote control
feature. It can change a huge amount of things on the fly: see the
- [200]-remote and [201]-query options. To shut down the running x11vnc
+ [198]-remote and [199]-query options. To shut down the running x11vnc
server just type "x11vnc -R stop". To disconnect all clients do
"x11vnc -R disconnect:all", etc.
- For older versions: If the [202]-forever option has not been supplied,
+ For older versions: If the [200]-forever option has not been supplied,
x11vnc will automatically exit after the first client disconnects. In
general you will have to kill the x11vnc process This can be done via:
"kill NNNNN" (where NNNNN is the x11vnc process id number found from
ps(1)), or "pkill x11vnc", or "killall x11vnc" (Linux only).
- If you have not put x11vnc in the background via the [203]-bg option
+ If you have not put x11vnc in the background via the [201]-bg option
or shell & operator, then simply press Ctrl-C in the shell where
x11vnc is running to stop it. Potential Gotcha: If somehow your
Keypress of Ctrl-C went through x11vnc to the Xserver that then
@@ -1739,14 +1754,14 @@ TrueColor defdepth 24
Tapping the stuck key (either via a new x11vnc or at the physical
console) will release it from the stuck state. If the keyboard seems
to be acting strangely it is often fixed by tapping Ctrl, Shift, and
- Alt. Alternatively, the [204]-clear_mods option and [205]-clear_keys
+ Alt. Alternatively, the [202]-clear_mods option and [203]-clear_keys
option can be used to release pressed keys at startup and exit.
Q-22: Can I change settings in x11vnc without having to restart it?
Can I remote control it?
- Look at the [206]-remote (same as -R) and [207]-query (same as -Q)
+ Look at the [204]-remote (same as -R) and [205]-query (same as -Q)
options added in the Dec/2004 libvncserver CVS. They allow nearly
everything to be changed dynamically and settings to be queried.
Examples: "x11vnc -R shared", "x11vnc -R forever", "x11vnc -R
@@ -1758,7 +1773,7 @@ TrueColor defdepth 24
be possible.
There is also a simple tcl/tk gui based on this remote control
- mechanism. See the [208]-gui option for more info.
+ mechanism. See the [206]-gui option for more info.
[Security and Permissions]
@@ -1770,12 +1785,12 @@ TrueColor defdepth 24
vncpasswd(1) program from those packages. The libvncserver package
also comes with a simple program: storepasswd in the examples
directory. And as of Jun/2004 in the libvncserver CVS x11vnc supports
- the -storepasswd "pass" "file" [209]option, which is the the same
+ the -storepasswd "pass" "file" [207]option, which is the the same
functionality of storepasswd. Be sure to quote the "pass" if it
contains shell meta characters, spaces, etc. Example:
x11vnc -storepasswd 'sword*fish' $HOME/myvncpasswd
- You then use the password via the x11vnc option: [210]-rfbauth
+ You then use the password via the x11vnc option: [208]-rfbauth
$HOME/myvncpasswd
Compared to vncpasswd(1) the latter two methods are a somewhat unsafe
@@ -1784,7 +1799,7 @@ TrueColor defdepth 24
out for the command winding up in your shell's history file (history
-c is often a way to clear it).
- x11vnc also has the [211]-passwdfile and -passwd/-viewpasswd plain
+ x11vnc also has the [209]-passwdfile and -passwd/-viewpasswd plain
text (i.e. not obscured like the -rfbauth VNC passwords) password
options.
@@ -1793,13 +1808,13 @@ TrueColor defdepth 24
and the other for view-only access to the display?
Yes, as of May/2004 in the libvncserver CVS there is the
- [212]-viewpasswd option to supply the view-only password. Note the
- full-access password option [213]-passwd must be supplied at the same
+ [210]-viewpasswd option to supply the view-only password. Note the
+ full-access password option [211]-passwd must be supplied at the same
time. E.g.: -passwd sword -viewpasswd fish.
To avoid specifying the passwords on the command line (where they
could be observed via the ps(1) command by any user) you can use the
- [214]-passwdfile option to specify a file containing plain text
+ [212]-passwdfile option to specify a file containing plain text
passwords. Presumably this file is readable only by you, and ideally
it is located on the machine x11vnc is run on (to avoid being snooped
on over the network). The first line of this file is the full-access
@@ -1807,7 +1822,7 @@ TrueColor defdepth 24
it is taken as the view-only password. (use "__EMPTY__" to supply an
empty one).
- View-only passwords currently do not work for the [215]-rfbauth
+ View-only passwords currently do not work for the [213]-rfbauth
password option (standard VNC password storing mechanism). FWIW, note
that although the output (usually placed in $HOME/.vnc/passwd) by the
vncpasswd or storepasswd programs (or from x11vnc -storepasswd) looks
@@ -1821,7 +1836,7 @@ TrueColor defdepth 24
some users just be able to move the mouse, but not click or type
anything?
- As of Feb/2005, the [216]-input option allows you to do this. "K",
+ As of Feb/2005, the [214]-input option allows you to do this. "K",
"M", and "B" stand for Keystroke, Mouse-motion, and Button-clicks,
respectively. The setting: "-input M" makes attached viewers only able
to move the mouse. "-input KMB,M" lets normal clients do everything
@@ -1837,15 +1852,15 @@ TrueColor defdepth 24
These defaults are simple safety measures to avoid someone unknowingly
leaving his X11 desktop exposed (to the internet, say) for long
- periods of time. Use the [217]-forever option (aka -many) to have
+ periods of time. Use the [215]-forever option (aka -many) to have
x11vnc wait for more connections after the first client disconnects.
- Use the [218]-shared option to have x11vnc allow multiple clients to
+ Use the [216]-shared option to have x11vnc allow multiple clients to
connect simultaneously.
- Recommended additional safety measures include using ssh ([219]see
+ Recommended additional safety measures include using ssh ([217]see
above), stunnel, or a VPN to authenticate and encrypt the viewer
- connections or to at least use the -rfbauth passwd-file [220]option to
- use VNC password protection (or [221]-passwdfile) It is up to you to
+ connections or to at least use the -rfbauth passwd-file [218]option to
+ use VNC password protection (or [219]-passwdfile) It is up to you to
apply these security measures, they will not be done for you
automatically.
@@ -1853,7 +1868,7 @@ TrueColor defdepth 24
Q-27: Can I limit which machines incoming VNC clients can connect
from?
- Yes, look at the [222]-allow and [223]-localhost options to limit
+ Yes, look at the [220]-allow and [221]-localhost options to limit
connections by hostname or IP address. E.g.
x11vnc -allow 192.168.0.1,192.168.0.2
@@ -1865,7 +1880,7 @@ TrueColor defdepth 24
Note that -localhost is the same as "-allow 127.0.0.1"
For more control, build libvncserver with libwrap support
- [224](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
+ [222](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
for complete details.
@@ -1885,7 +1900,7 @@ TrueColor defdepth 24
is "vnc", e.g.:
vnc: 192.168.100.3 .example.com
- Note that if you run x11vnc out of [225]inetd you do not need to build
+ Note that if you run x11vnc out of [223]inetd you do not need to build
x11vnc with libwrap support because the /usr/sbin/tcpd reference in
/etc/inetd.conf handles the tcp_wrappers stuff.
@@ -1894,16 +1909,16 @@ TrueColor defdepth 24
internal LAN) rather than having it listen on all network interfaces
and relying on -allow to filter unwanted connections out?
- As of Mar/2005 in the libvncserver CVS, there is the "[226]-listen
+ As of Mar/2005 in the libvncserver CVS, there is the "[224]-listen
ipaddr" option that enables this. For ipaddr either supply the desired
network interface's IP address (or use a hostname that resolves to it)
or use the string "localhost". For additional filtering simultaneously
- use the "[227]-allow host1,..." option to allow only specific hosts
+ use the "[225]-allow host1,..." option to allow only specific hosts
in.
This option is useful if you want insure that no one can even begin a
dialog with x11vnc from untrusted network interfaces (e.g. ppp0). The
- option [228]-localhost now implies "-listen localhost" since that is
+ option [226]-localhost now implies "-listen localhost" since that is
what most people expect it to do.
@@ -1911,24 +1926,24 @@ TrueColor defdepth 24
interface, how I can occasionally allow in a non-localhost via the
allowonce remote control command?
- To do this specify "[229]-allow localhost". Unlike [230]-localhost
+ To do this specify "[227]-allow localhost". Unlike [228]-localhost
this will leave x11vnc listening on all interfaces (but of course only
allowing in local connections, e.g. ssh redirs). Then you can later
run "x11vnc -R allowonce:somehost" or use to gui to permit a one-shot
connection from a remote host.
Note that if you do a lot of changing of the listening interface
- ([231]-listen option) via remote control or gui, you may need to also
- manually adjust the [232]-allow list if you unexpectedly get into a
+ ([229]-listen option) via remote control or gui, you may need to also
+ manually adjust the [230]-allow list if you unexpectedly get into a
state where the allow list cannot match any hosts that would be coming
- in on the listening interface. If you just toggle [233]-localhost on
+ in on the listening interface. If you just toggle [231]-localhost on
and off x11vnc should see to it that you never get into such a state.
Q-31: How can I tunnel my connection to x11vnc via an encrypted SSH
channel between two Unix machines?
- See the description earlier on this page on [234]how to tunnel VNC via
+ See the description earlier on this page on [232]how to tunnel VNC via
SSH from Unix to Unix. A number of ways are described along with some
issues you may encounter.
@@ -1939,7 +1954,7 @@ TrueColor defdepth 24
Q-32: How can I tunnel my connection to x11vnc via an encrypted SSH
channel from Windows using an SSH client like Putty?
- [235]Above we described how to tunnel VNC via SSH from Unix to Unix,
+ [233]Above we described how to tunnel VNC via SSH from Unix to Unix,
you may want to review it. To do this from Windows using Putty it
would go something like this:
* In the Putty dialog window under 'Session' enter the hostname or
@@ -1962,8 +1977,8 @@ TrueColor defdepth 24
process in a BAT file including launching the VNC viewer by using the
plink Putty utility. Send us the script if you get that working.
- For extra protection feel free to run x11vnc with the [236]-localhost
- and [237]-rfbauth/[238]-passwdfile options.
+ For extra protection feel free to run x11vnc with the [234]-localhost
+ and [235]-rfbauth/[236]-passwdfile options.
If the machine you SSH into via Putty is not the same machine with the
X display you wish to view (e.g. your company provides incoming SSH
@@ -1972,9 +1987,9 @@ TrueColor defdepth 24
you'll need to do a second login (ssh or rsh) to the workstation
machine 'otherhost' and then start up x11vnc on it.
- As discussed [239]above another option is to first start the VNC
+ As discussed [237]above another option is to first start the VNC
viewer in "listen" mode, and then launch x11vnc with the
- "[240]-connect localhost" option to establish the reverse connection.
+ "[238]-connect localhost" option to establish the reverse connection.
In this case a Remote port redirection (not Local) is needed for port
5500 instead of 5900 (i.e. 'Source port: 5500' and
'Destination: localhost:5500' for a Remote connection).
@@ -1985,7 +2000,7 @@ TrueColor defdepth 24
some clients view-only? How about running an arbitrary program to make
the decisions?
- Yes, look at the "[241]-accept command" option, it allows you to
+ Yes, look at the "[239]-accept command" option, it allows you to
specify an external command that is run for each new client. (use
quotes around the command if it contains spaces, etc.). If the
external command returns 0 the client is accepted, otherwise the
@@ -2004,7 +2019,7 @@ TrueColor defdepth 24
own simple popup window. To accept the client press "y" or click mouse
on the "Yes" button. To reject the client press "n" or click mouse on
the "No" button. To accept the client View-only, press "v" or click
- mouse on the "View" button. If the [242]-viewonly option has been
+ mouse on the "View" button. If the [240]-viewonly option has been
supplied, the "View" action will not be present: the whole display is
view only in that case.
@@ -2020,7 +2035,7 @@ TrueColor defdepth 24
program to prompt the user whether the client should be accepted or
not. This requires that you have xmessage installed and available via
PATH. In case it is not already on your system, the xmessage program
- is available at [243]ftp://ftp.x.org/
+ is available at [241]ftp://ftp.x.org/
To include view-only decisions for the external commands, prefix the
command something like this: "yes:0,no:*,view:3 mycommand ..." This
@@ -2059,7 +2074,7 @@ elif [ $rc = 4 ]; then
fi
exit 1
- Stefan Radman has written a nice dtksh script [244]dtVncPopup for use
+ Stefan Radman has written a nice dtksh script [242]dtVncPopup for use
in CDE environments to do the same sort of thing. Information on how
to use it is found at the top of the file. He encourages you to
provide feedback to him to help improve the script.
@@ -2068,7 +2083,7 @@ exit 1
popup is being run, so attached clients will not receive screen
updates, etc during this period.
- To run a command when a client disconnects, use the "[245]-gone
+ To run a command when a client disconnects, use the "[243]-gone
command" option. This is for the user's convenience only: the return
code of the command is not interpreted by x11vnc. The same environment
variables are set as in "-accept command" (except that RFB_MODE will
@@ -2083,13 +2098,13 @@ exit 1
such support.
One approximate method involves starting x11vnc with the
- [246]-localhost option. This basically requires the viewer user to log
+ [244]-localhost option. This basically requires the viewer user to log
into the workstation where x11vnc is running via their Unix username
and password, and then somehow set up a port redirection of his
vncviewer connection to make it appear to emanate from the local
machine. As discussed above, ssh is useful for this: ssh -l username
-L 5900:localhost:5900 hostname ... See the ssh wrapper scripts
- mentioned [247]elsewhere on this page. Of course a malicious user
+ mentioned [245]elsewhere on this page. Of course a malicious user
could allow other users to get in through his channel, but that is a
problem with every method. Another thing to watch out for is a
malicious user on the viewer side (where ssh is running) trying to
@@ -2098,7 +2113,7 @@ exit 1
Regarding limiting the set of Unix usernames who can connect, the
traditional way would be to further require a VNC password to supplied
(-rfbauth, -passwd, etc). A scheme that avoids a second password
- involves using the [248]-accept option that runs a program to examine
+ involves using the [246]-accept option that runs a program to examine
the connection information to determine which user is connecting from
the local machine. For example, the program could use the ident
service on the local machine (normally ident should not be trusted
@@ -2131,7 +2146,7 @@ exit 1 # reject it
display manager like gdm(1). Can I have x11vnc later switch to a
different user?
- As of Feb/2005 x11vnc has the [249]-users option that allows things
+ As of Feb/2005 x11vnc has the [247]-users option that allows things
like this. Please read the documentation on it (in the x11vnc -help
output) carefully for features and caveats. It's use can often
decrease security unless care is taken. A nice use of it is "-users
@@ -2152,7 +2167,7 @@ exit 1 # reject it
In any event, as of Jun/2004 there is an experimental utility to make
it more difficult for nosey people to see your x11vnc activities. The
- source for it is [250]blockdpy.c The idea behind it is simple (but
+ source for it is [248]blockdpy.c The idea behind it is simple (but
obviously not bulletproof): when a VNC client attaches to x11vnc put
the display monitor in the DPMS "off" state, if the DPMS state ever
changes immediately start up the screen-lock program. The x11vnc user
@@ -2168,8 +2183,8 @@ exit 1 # reject it
bulletproof. A really robust solution would likely require X server
and perhaps even video hardware support.
- The blockdpy utility is launched by the [251]-accept option and told
- to exit via the [252]-gone option (the vnc client user should
+ The blockdpy utility is launched by the [249]-accept option and told
+ to exit via the [250]-gone option (the vnc client user should
obviously re-lock the screen before disconnecting!). Instructions can
be found in the source code for the utility at the above link.
@@ -2177,7 +2192,7 @@ exit 1 # reject it
Q-37: Can I have x11vnc automatically lock the screen when I
disconnect the VNC viewer?
- Yes, a user mentions he uses the [253]-gone option under CDE to run a
+ Yes, a user mentions he uses the [251]-gone option under CDE to run a
screen lock program:
x11vnc -display :0 -forever -gone 'dtaction LockDisplay'
@@ -2200,11 +2215,11 @@ exit 1 # reject it
permissions to connect to the X display.
Here are some ideas:
- * Use the description under "Continuously" in the [254]FAQ on x11vnc
+ * Use the description under "Continuously" in the [252]FAQ on x11vnc
and Display Managers
- * Use the description in the [255]FAQ on x11vnc and inetd(1)
+ * Use the description in the [253]FAQ on x11vnc and inetd(1)
* Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc)
- * Although less reliable, see the [256]x11vnc_loop rc.local hack
+ * Although less reliable, see the [254]x11vnc_loop rc.local hack
below.
The display manager scheme will not be specific to which user has the
@@ -2235,7 +2250,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
while running x11vnc as root, e.g. for the gnome display manager, gdm:
x11vnc -auth /var/gdm/:0.Xauth -display :0
- (the [257]-auth option sets the XAUTHORITY variable for you).
+ (the [255]-auth option sets the XAUTHORITY variable for you).
There will be a similar thing for xdm using however a different auth
directory path (perhaps something like
@@ -2260,7 +2275,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
auth file should be in /var/dt), you'll also need to add something
like Dtlogin*grabServer:False to the Xconfig file
(/etc/dt/config/Xconfig or /usr/dt/config/Xconfig on Solaris, see
- [258]the example at the end of this FAQ). Then restart dtlogin, e.g.:
+ [256]the example at the end of this FAQ). Then restart dtlogin, e.g.:
/etc/init.d/dtlogin stop; /etc/init.d/dtlogin start or reboot.
Continuously. Have x11vnc reattach each time the X server is
@@ -2314,7 +2329,7 @@ rever -bg
Then restart: /usr/sbin/gdm-restart (or reboot). The
KillInitClients=false setting is important: without it x11vnc will be
- killed immediately after the user logs in. Here are [259]full details
+ killed immediately after the user logs in. Here are [257]full details
on how to configure gdm
_________________________________________________________________
@@ -2356,13 +2371,13 @@ rever -bg
If you do not want to deal with any display manager startup scripts,
here is a kludgey script that can be run manually or out of a boot
- file like rc.local: [260]x11vnc_loop It will need some local
+ file like rc.local: [258]x11vnc_loop It will need some local
customization before running. Because the XAUTHORITY auth file must be
guessed by this script, use of the display manager script method
described above is greatly preferred.
If the machine is a traditional Xterminal you may want to read
- [261]this FAQ.
+ [259]this FAQ.
Q-40: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
@@ -2372,7 +2387,7 @@ rever -bg
5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh
- where the shell script /usr/local/bin/x11vnc_sh uses the [262]-inetd
+ where the shell script /usr/local/bin/x11vnc_sh uses the [260]-inetd
option and looks something like (you'll need to customize to your
settings).
#!/bin/sh
@@ -2384,13 +2399,13 @@ rever -bg
(otherwise the standard error also goes to the VNC vncviewer, and that
confuses it greatly). If you do not use a wrapper script as above but
rather call x11vnc directly in /etc/inetd.conf and do not redirect
- stderr to a file, then you must specify the -q (aka [263]-quiet)
+ stderr to a file, then you must specify the -q (aka [261]-quiet)
option: "/usr/local/bin/x11vnc -q -inetd ..." or use "-o logfile" to
collect the output in a file. The wrapper script with redirection to a
log file is the recommended method because the errors and warnings
printed out are very useful in troubleshooting problems.
- Note also the need to set XAUTHORITY via [264]-auth to point to the
+ Note also the need to set XAUTHORITY via [262]-auth to point to the
MIT-COOKIE auth file to get permission to connect to the X display
(setting and exporting the XAUTHORITY variable accomplishes the same
thing). See the x11vnc_loop file in the previous question for more
@@ -2438,7 +2453,7 @@ service x11vncservice
web browser?
To have x11vnc serve up a Java VNC viewer applet to any web browsers
- that connect to it, run x11vnc with this [265]option:
+ that connect to it, run x11vnc with this [263]option:
-httpdir /path/to/the/java/classes/dir
(this directory will contain the files index.vnc and, for example,
@@ -2468,7 +2483,7 @@ service x11vncservice
As of Mar/2004 in the libvncserver CVS x11vnc supports reverse
connections. On Unix one starts the VNC viewer in listen mode:
vncviewer -listen (see your documentation for Windows, etc), and then
- starts up x11vnc with the [266]-connect option. To connect immediately
+ starts up x11vnc with the [264]-connect option. To connect immediately
at x11vnc startup time use the "-connect host:port" option (use commas
for a list of hosts to connect to). The ":port" is optional (default
is 5500). If a file is specified instead: -connect /path/to/some/file
@@ -2476,7 +2491,7 @@ service x11vncservice
hosts to connect to.
To use the vncconnect(1) program (from the core VNC package at
- www.realvnc.com) specify the [267]-vncconnect option to x11vnc (Note:
+ www.realvnc.com) specify the [265]-vncconnect option to x11vnc (Note:
as of Dec/2004 -vncconnect is now the default). vncconnect(1) must be
pointed to the same X11 DISPLAY as x11vnc (since it uses X properties
to communicate with x11vnc). If you do not have or do not want to get
@@ -2518,7 +2533,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
There are some annoyances WRT Xvfb though. The default keyboard
mapping seems to be very poor. One should run x11vnc with
- [268]-add_keysyms option to have keysyms added automatically. Also, to
+ [266]-add_keysyms option to have keysyms added automatically. Also, to
add the Shift_R and Control_R modifiers something like this is needed:
#!/bin/sh
xmodmap -e "keycode any = Shift_R"
@@ -2545,7 +2560,7 @@ xmodmap -e "add Control = Control_L Control_R"
An X server can be started on the headless machine (sometimes this
requires configuring the X server to not fail if it cannot detect a
keyboard or mouse, see the next paragraph). Then you can export that X
- display via x11vnc (e.g. see [269]this FAQ) and access it from
+ display via x11vnc (e.g. see [267]this FAQ) and access it from
anywhere on the network via a VNC viewer.
Some tips on getting X servers to start on machines without keyboard
@@ -2588,7 +2603,7 @@ xmodmap -e "add Control = Control_L Control_R"
19/03/2004 10:10:58 error creating tile-row shm for len=4
19/03/2004 10:10:58 reverting to single_copytile mode
- Here is a shell script [270]shm_clear to list and prompt for removal
+ Here is a shell script [268]shm_clear to list and prompt for removal
of your unattached shm segments (attached ones are skipped). I use it
while debugging x11vnc (I use "shm_clear -y" to assume "yes" for each
prompt). If x11vnc is regularly not cleaning up its shm segments,
@@ -2622,35 +2637,35 @@ ied)
in /etc/system. See the next paragraph for more workarounds.
To minimize the number of shm segments used by x11vnc try using the
- [271]-onetile option (corresponds to only 3 shm segments used, and
+ [269]-onetile option (corresponds to only 3 shm segments used, and
adding -fs 1.0 knocks it down to 2). If you are having much trouble
with shm segments, consider disabling shm completely via the
- [272]-noshm option. Performance will be somewhat degraded but when
+ [270]-noshm option. Performance will be somewhat degraded but when
done over local machine sockets it should be acceptable (see an
- [273]earlier question discussing -noshm).
+ [271]earlier question discussing -noshm).
Q-46: How can I make x11vnc use less system resources?
- The [274]-nap and "[275]-wait n" (where n is the sleep between polls
+ The [272]-nap and "[273]-wait n" (where n is the sleep between polls
in milliseconds, the default is 30 or so) option are good places to
start. Reducing the X server bits per pixel depth (e.g. to 16bpp or
even 8bpp) will further decrease memory I/O and network I/O. Using the
- [276]-onetile option will use less memory and use fewer shared memory
- slots (add [277]-fs 1.0 for one less slot).
+ [274]-onetile option will use less memory and use fewer shared memory
+ slots (add [275]-fs 1.0 for one less slot).
Q-47: How can I make x11vnc use MORE system resources?
- You can try [278]-threads and dial down the wait time (e.g. -wait 1)
- and possibly dial down [279]-defer as well. Note that if you try to
+ You can try [276]-threads and dial down the wait time (e.g. -wait 1)
+ and possibly dial down [277]-defer as well. Note that if you try to
increase the "frame rate" too much you can bog down the server end
with the extra work it needs to do compressing the framebuffer data,
etc.
That said, it is possible to "stream" video via x11vnc if the video
window is small enough. E.g. a 256x192 xawtv TV capture window (using
- the x11vnc [280]-id option) can be streamed over a LAN or wireless at
+ the x11vnc [278]-id option) can be streamed over a LAN or wireless at
a reasonable frame rate.
@@ -2666,7 +2681,7 @@ ied)
* Use a smaller desktop size (e.g. 1024x768 instead of 1280x1024)
* Make sure the desktop background is a solid color (the background
is resent every time it is re-exposed). Consider using the
- [281]-solid [color] option.
+ [279]-solid [color] option.
* Configure your window manager or desktop "theme" to not use fancy
images, shading, and gradients for the window decorations, etc.
Disable Opaque moves, resizes, and animations.
@@ -2682,7 +2697,7 @@ ied)
worth it, but could be of use in some situations.
VNC viewer parameters:
- * Use a [282]TightVNC enabled viewer!
+ * Use a [280]TightVNC enabled viewer!
* Make sure the tight encoding is being used (look at vncviewer and
x11vnc outputs)
* Request 8 bits per pixel using -bgr233 (up to 4X speedup over
@@ -2700,19 +2715,19 @@ ied)
vncviewer to be very slow)
x11vnc parameters:
- * Try using [283]-nodragging (no screen updates when dragging mouse,
+ * Try using [281]-nodragging (no screen updates when dragging mouse,
but sometimes you miss visual feedback)
- * Try the [284]-progressive pixelheight mode with the block
+ * Try the [282]-progressive pixelheight mode with the block
pixelheight 100 or so (delays sending vertical blocks since they
may change while viewer is receiving earlier ones)
- * Set [285]-fs 1.0 (disables fullscreen updates)
- * Try increasing [286]-wait or [287]-defer (reduces the maximum
+ * Set [283]-fs 1.0 (disables fullscreen updates)
+ * Try increasing [284]-wait or [285]-defer (reduces the maximum
"frame rate", but won't help much for large screen changes)
- * If you just want to watch one (simple) window use [288]-id (cuts
+ * If you just want to watch one (simple) window use [286]-id (cuts
down extraneous polling and updates, but can be buggy or
insufficient)
- * Set [289]-nosel (disables all clipboard selection exchange)
- * Use [290]-nocursor and [291]-nocursorpos (repainting the remote
+ * Set [287]-nosel (disables all clipboard selection exchange)
+ * Use [288]-nocursor and [289]-nocursorpos (repainting the remote
cursor position and shape takes resources and round trips)
@@ -2727,7 +2742,7 @@ ied)
second to read the changes induce from moving a large window, if this
to be done a number of times in succession the window or scroll
appears to "lurch" forward). See the description in the
- [292]-pointer_mode option for more info. The next bottleneck is
+ [290]-pointer_mode option for more info. The next bottleneck is
compressing all of these changes and sending them out to connected
viewers, however the VNC protocol is pretty much self-adapting with
respect to that (updates are only packaged and sent when viewers ask
@@ -2737,25 +2752,25 @@ ied)
tree. The default should now be much better than before and dragging
small windows around should no longer be a huge pain. If for some
reason these changes make matters worse, you can go back to the old
- way via the "[293]-pointer_mode 1" option.
+ way via the "[291]-pointer_mode 1" option.
- Also added was the [294]-nodragging option that disables all screen
+ Also added was the [292]-nodragging option that disables all screen
updates while dragging with the mouse (i.e. mouse motion with a button
held down). This gives the snappiest response, but might be undesired
in some circumstances when you want to see the visual feedback while
dragging (e.g. menu traversal or text selection).
- As of Dec/2004 in the libvncserver CVS the [295]-pointer_mode n option
+ As of Dec/2004 in the libvncserver CVS the [293]-pointer_mode n option
was introduced. n=1 is the original mode, n=2 an improvement, etc..
See the -pointer_mode n help for more info.
- Also, in some circumstances the [296]-threads option can improve
+ Also, in some circumstances the [294]-threads option can improve
response considerably. Be forewarned that if more than one vncviewer
is connected at the same time then libvncserver may not be thread safe
(try to get the viewers to use different VNC encodings, e.g. tight and
ZRLE).
- See the [297]wireframe FAQ below for a scheme to sweep this problem
+ See the [295]wireframe FAQ below for a scheme to sweep this problem
under the rug for window moves or resizes.
@@ -2770,13 +2785,13 @@ ied)
shown. When the window move/resize stops, it returns to normal
processing: you should only see the window appear in the new position.
This spares you from interacting with a "lurching" window between all
- of the intermediate steps. BTW the lurching is due to [298]slow video
+ of the intermediate steps. BTW the lurching is due to [296]slow video
card read rates. A displacement, even a small one, of a large window
requires a non-negligible amount of time, a good fraction of a second,
to read in from the hardware framebuffer.
The mode is currently on by default because most people are inflicted
- with the problem. It can be disabled with the [299]-nowireframe
+ with the problem. It can be disabled with the [297]-nowireframe
option. Why might one want to turn off the wireframing? Since x11vnc
is merely guessing when windows are being moved/resized, it may guess
poorly for your window-manager or desktop, or even for the way you
@@ -2816,13 +2831,13 @@ ied)
* Maximum time to show a wireframe animation.
* Minimum time between sending wireframe outlines.
- See the [300]"-wireframe tweaks" option for more details. On a slow
+ See the [298]"-wireframe tweaks" option for more details. On a slow
link, e.g. dialup modem, you may want to increase all four of these
times, e.g. double them from the defaults.
CopyRect encoding: In addition to the above there is the
- [301]"-wirecopyrect mode" option. It is also on by default. This
+ [299]"-wirecopyrect mode" option. It is also on by default. This
instructs x11vnc to not only show show the wireframe animation, but to
also instruct all connected VNC viewers to locally translate the
window image data from the original position to the new position on
@@ -2886,13 +2901,13 @@ ied)
DAMAGE rectangles to contain real damage. The larger rectangles are
only used as hints to focus the traditional scanline polling (i.e. if
a scanline doesn't intersect a recent DAMAGE rectangle, the scan is
- skipped). You can use the "[302]-xd_area A" option to adjust the size
+ skipped). You can use the "[300]-xd_area A" option to adjust the size
of the trusted DAMAGE rectangles. The default is 20000 pixels (e.g. a
140x140 square, etc). Use "-xd_area 0" to disable the cutoff and trust
all DAMAGE rectangles.
- The option "[303]-xd_mem f" may also be of use in tuning the
- algorithm. To disable using DAMAGE entirely use "[304]-noxdamage".
+ The option "[301]-xd_mem f" may also be of use in tuning the
+ algorithm. To disable using DAMAGE entirely use "[302]-noxdamage".
[Mouse Cursor Shapes]
@@ -2910,16 +2925,16 @@ ied)
this is because the cursor shape is often downloaded to the graphics
hardware (video card), but I could be mistaken.
- A simple kludge is provided by the "[305]-cursor X" option that
+ A simple kludge is provided by the "[303]-cursor X" option that
changes the cursor when the mouse is on the root background (or any
window has the same cursor as the root background). Note that desktops
like GNOME or KDE often cover up the root background, so this won't
- work for those cases. Also see the "[306]-cursor some" option for
+ work for those cases. Also see the "[304]-cursor some" option for
additional kludges.
Note that as of Aug/2004 in the libvncserver CVS, on Solaris using the
SUN_OVL overlay extension and IRIX, x11vnc can show the correct mouse
- cursor when the [307]-overlay option is supplied. See [308]this FAQ
+ cursor when the [305]-overlay option is supplied. See [306]this FAQ
for more info.
Also as of Dec/2004 in the libvncserver CVS XFIXES X extension support
@@ -2927,7 +2942,7 @@ ied)
XFIXES fixes the problem of the cursor-shape being write-only: x11vnc
can now query the X server for the current shape and send it back to
the connected viewers. XFIXES is available on recent Linux Xorg based
- distros and [309]Solaris 10.
+ distros and [307]Solaris 10.
The only XFIXES issue is the handling of alpha channel transparency in
cursors. If a cursor has any translucency then in general it must be
@@ -2935,7 +2950,7 @@ ied)
cursor transparency can also handled exactly: when the VNC Viewer
requires the cursor shape be drawn into the VNC framebuffer or if you
apply a patch to your VNC Viewer to extract hidden alpha channel data
- under 32bpp. [310]Details can be found here.
+ under 32bpp. [308]Details can be found here.
Q-53: When using XFIXES cursorshape mode, some of the cursors look
@@ -2968,17 +2983,17 @@ ied)
for most cursor themes and you don't have to worry about it.
In case it still looks bad for your cursor theme, there are (of
- course!) some tunable parameters. The "[311]-alphacut n" option lets
+ course!) some tunable parameters. The "[309]-alphacut n" option lets
you set the threshold "n" (between 0 and 255): cursor pixels with
alpha values below n will be considered completely transparent while
values equal to or above n will be completely opaque. The default is
- 240. The "[312]-alphafrac f" option tries to correct individual
+ 240. The "[310]-alphafrac f" option tries to correct individual
cursors that did not fare well with the default -alphacut value: if a
cursor has less than fraction f (between 0.0 and 1.0) of its pixels
selected by the default -alphacut, the threshold is lowered until f of
its pixels are selected. The default fraction is 0.33.
- Finally, there is an option [313]-alpharemove that is useful for
+ Finally, there is an option [311]-alpharemove that is useful for
themes where many cursors are light colored (e.g. "whiteglass").
XFIXES returns the cursor data with the RGB values pre-multiplied by
the alpha value. If the white cursors look too grey, specify
@@ -2994,11 +3009,11 @@ ied)
send the alpha channel data to libvncserver. However, this data will
only be used for VNC clients that do not support the
CursorShapeUpdates VNC extension (or have disabled it). It can be
- disabled for all clients with the [314]-nocursorshape x11vnc option.
+ disabled for all clients with the [312]-nocursorshape x11vnc option.
In this case the cursor is drawn, correctly blended with the
background, into the VNC framebuffer before being sent out to the
client. So the alpha blending is done on the x11vnc side. Use the
- [315]-noalphablend option to disable this behavior (always approximate
+ [313]-noalphablend option to disable this behavior (always approximate
transparent cursors with opaque RGB values).
The CursorShapeUpdates VNC extension complicates matters because the
@@ -3026,9 +3041,9 @@ ied)
Q-55: Why does the mouse arrow just stay in one corner in my
vncviewer, whereas my cursor (that does move) is just a dot?
- This default takes advantage of a [316]tightvnc extension
+ This default takes advantage of a [314]tightvnc extension
(CursorShapeUpdates) that allows specifying a cursor image shape for
- the local VNC viewer. You may disable it with the [317]-nocursor
+ the local VNC viewer. You may disable it with the [315]-nocursor
option to x11vnc if your viewer does not have this extension.
Note: as of Aug/2004 in the libvncserver CVS this should be fixed: the
@@ -3042,18 +3057,18 @@ ied)
clients (i.e. passive viewers can see the mouse cursor being moved
around by another viewer)?
- Use the [318]-cursorpos option when starting x11vnc. A VNC viewer must
+ Use the [316]-cursorpos option when starting x11vnc. A VNC viewer must
support the Cursor Positions Updates for the user to see the mouse
motions (the TightVNC viewers support this). As of Aug/2004 in the
- libvncserver CVS -cursorpos is the default. See also [319]-nocursorpos
- and [320]-nocursorshape.
+ libvncserver CVS -cursorpos is the default. See also [317]-nocursorpos
+ and [318]-nocursorshape.
Q-57: Is it possible to swap the mouse buttons (e.g. left-handed
operation), or arbitrarily remap them? How about mapping button clicks
to keystrokes, e.g. to partially emulate Mouse wheel scrolling?
- You can remap the mouse buttons via something like: [321]-buttonmap
+ You can remap the mouse buttons via something like: [319]-buttonmap
13-31 (or perhaps 12-21). Also, note that xmodmap(1) lets you directly
adjust the X server's button mappings, but in some circumstances it
might be more desirable to have x11vnc do it.
@@ -3061,7 +3076,7 @@ ied)
One user had an X server with only one mouse button(!) and was able to
map all of the VNC client mouse buttons to it via: -buttonmap 123-111.
- Note that the [322]-debug_pointer option prints out much info for
+ Note that the [320]-debug_pointer option prints out much info for
every mouse/pointer event and is handy in solving problems.
To map mouse button clicks to keystrokes you can use the alternate
@@ -3083,7 +3098,7 @@ ied)
Exactly what keystroke "scrolling" events they should be bound to
depends on one's taste. If this method is too approximate, one could
- consider not using [323]-buttonmap but rather configuring the X server
+ consider not using [321]-buttonmap but rather configuring the X server
to think it has a mouse with 5 buttons even though the physical mouse
does not.
@@ -3099,12 +3114,21 @@ ied)
-buttonmap 3-:Shift_L+k+Shift_L+a+r+l+space+Shift_L+r+Shift_L+u+n+g+e:
(yes, this is getting a little silly).
+
+ BTW, Coming the other way around, if the machine you are sitting at
+ does not have a mouse wheel, but the remote machine does (or at least
+ has 5 buttons configured), this key remapping can be useful:
+ -remap Super_R-Button4,Menu-Button5
+
+ you just tap those two keys to get the mouse wheel scrolls (this is
+ more useful than the Up and Down arrow keys because a mouse wheel
+ "click" usually gives a multi-line scroll).
[Keyboard Issues]
Q-58: How can I get my AltGr and Shift modifiers to work between
keyboards for different languages?
- The option [324]-modtweak should be of some use for this. It is a mode
+ The option [322]-modtweak should be of some use for this. It is a mode
that monitors the state of the Shift and AltGr Modifiers and tries to
deduce the correct keycode to send, possibly by sending fake modifier
key presses and releases in addition to the actual keystroke.
@@ -3113,17 +3137,17 @@ ied)
default (use -nomodtweak to get the old behavior). This was done
because it was noticed on newer XFree86 setups even on bland "us"
keyboards like "pc104 us" XFree86 included a "ghost" key with both "<"
- and ">" it. This key does not exist on the keyboard (see [325]this FAQ
+ and ">" it. This key does not exist on the keyboard (see [323]this FAQ
for more info). Without -modtweak there was then an ambiguity in the
reverse map keysym => keycode, making it so the "<" symbol could not
be typed.
- Also see the [326]FAQ about the -xkb option for a more powerful method
+ Also see the [324]FAQ about the -xkb option for a more powerful method
of modifier tweaking for use on X servers with the XKEYBOARD
extension.
When trying to resolve keyboard mapping problems, note that the
- [327]-debug_keyboard option prints out much info for every keystroke
+ [325]-debug_keyboard option prints out much info for every keystroke
and so can be useful debugging things.
@@ -3174,17 +3198,17 @@ ied)
-remap less-comma
These are convenient in that they do not modify the actual X server
- settings. The former ([328]-modtweak) is a mode that monitors the
+ settings. The former ([326]-modtweak) is a mode that monitors the
state of the Shift and AltGr modifiers and tries to deduce the correct
keycode sequence to send. Since Jul/2004 -modtweak is now the default.
- The latter ([329]-remap less-comma) is an immediate remapping of the
+ The latter ([327]-remap less-comma) is an immediate remapping of the
keysym less to the keysym comma when it comes in from a client (so
when Shift is down the comma press will yield "<").
- See also the [330]FAQ about the -xkb option as a possible workaround
+ See also the [328]FAQ about the -xkb option as a possible workaround
using the XKEYBOARD extension.
- Note that the [331]-debug_keyboard option prints out much info for
+ Note that the [329]-debug_keyboard option prints out much info for
every keystroke to aid debugging keyboard problems.
@@ -3209,7 +3233,7 @@ ied)
In both cases no AltGr is sent to the VNC server, but we know AltGr is
needed on the physical international keyboard to type a "@".
- This all worked fine with x11vnc running with the [332]-modtweak
+ This all worked fine with x11vnc running with the [330]-modtweak
option (it figures out how to adjust the Modifier keys (Shift or
AltGr) to get the "@"). However it fails under recent versions of
XFree86 (and the X.org fork). These run the XKEYBOARD extension by
@@ -3227,7 +3251,7 @@ ied)
* there is a new option -xkb to use the XKEYBOARD extension API to
do the Modifier key tweaking.
- The [333]-xkb option seems to fix all of the missing keys: "@", "<",
+ The [331]-xkb option seems to fix all of the missing keys: "@", "<",
">", etc.: it is recommended that you try it if you have this sort of
problem. Let us know if there are any remaining problems (see the next
paragraph for some known problems). If you specify the -debug_keyboard
@@ -3245,7 +3269,7 @@ ied)
was attached to keycode 93 (no physical key generates this
keycode) while ISO_Level3_Shift was attached to keycode 113. The
keycode skipping option was used to disable the ghost key:
- [334]-skip_keycodes 93
+ [332]-skip_keycodes 93
* In implementing -xkb we noticed that some characters were still
not getting through, e.g. "~" and "^". This is not really an
XKEYBOARD problem. What was happening was the VNC viewer was
@@ -3262,14 +3286,14 @@ ied)
What to do? In general the VNC protocol has not really solved this
problem: what should be done if the VNC viewer sends a keysym not
recognized by the VNC server side? Workarounds can possibly be
- created using the [335]-remap x11vnc option:
+ created using the [333]-remap x11vnc option:
-remap asciitilde-dead_tilde,asciicircum-dead_circumflex
etc. Use -remap filename if the list is long. Please send us your
workarounds for this problem on your keyboard. Perhaps we can have
x11vnc adjust automatically at some point. Also see the
- [336]-add_keysyms option in the next paragraph.
- * To complement the above workaround using the [337]-remap, an
- option [338]-add_keysyms was added. This option instructs x11vnc
+ [334]-add_keysyms option in the next paragraph.
+ * To complement the above workaround using the [335]-remap, an
+ option [336]-add_keysyms was added. This option instructs x11vnc
to bind any unknown Keysyms coming in from VNC viewers to unused
Keycodes in the X server. This modifies the global state of the X
server. When x11vnc exits it removes the extra keymappings it
@@ -3286,7 +3310,7 @@ ied)
Short answer: disable key autorepeating by running the command "xset r
off" on the Xserver where x11vnc is run (restore via "xset r on") or
- use the new (Jul/2004) [339]-norepeat x11vnc option. You will still
+ use the new (Jul/2004) [337]-norepeat x11vnc option. You will still
have autorepeating because that is taken care of on your VNC viewer
side. Update: as of Dec/2004 -norepeat is now the default. Use -repeat
to disable it.
@@ -3308,7 +3332,7 @@ ied)
off", does the problem go away?
The workaround is to manually apply "xset r off" and "xset r on" as
- needed, or to use the [340]-norepeat (which has since Dec/2004 been
+ needed, or to use the [338]-norepeat (which has since Dec/2004 been
made the default). Note that with X server autorepeat turned off the
VNC viewer side of the connection will (nearly always) do its own
autorepeating so there is no big loss here, unless someone is also
@@ -3319,7 +3343,7 @@ ied)
keystrokes!!
Are you using x11vnc to log in to an X session? (as described in
- [341]this FAQ) If so, x11vnc is starting before your session and it
+ [339]this FAQ) If so, x11vnc is starting before your session and it
disables autorepeat when you connect, but then after you log in your
session startup (GNOME, KDE, ...) could be resetting the autorepeat to
be on. Or it could be something inside your desktop trying to be
@@ -3343,7 +3367,7 @@ ied)
machine where I run the VNC viewer does not. Is there a way I can map
a local unused key to send an AltGr? How about a Compose key as well?
- Something like "[342]-remap Super_R-Mode_switch" x11vnc option may
+ Something like "[340]-remap Super_R-Mode_switch" x11vnc option may
work. Note that Super_R is the "Right Windoze(tm) Flaggie" key; you
may want to choose another. The -debug_keyboard option comes in handy
in finding keysym names (so does xev(1)).
@@ -3366,7 +3390,7 @@ ied)
Since xmodmap(1) modifies the X server mappings you may not want to do
this (because it affects local work on that machine). Something like
- the [343]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
+ the [341]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
needs, and does not modify the X server environment. Note that you
cannot send Alt_L in this case, maybe -remap Super_L-Meta_L would be a
better choice if the Super_L key is typically unused.
@@ -3377,7 +3401,7 @@ ied)
This can be done directly in some X servers using AccessX and
Pointer_EnableKeys, but is a bit awkward. It may be more convenient to
- have x11vnc do the remapping. This can be done via the [344]-remap
+ have x11vnc do the remapping. This can be done via the [342]-remap
option using the fake "keysyms" Button1, Button2, etc. as the "to"
keys (i.e. the ones after the "-")
@@ -3385,7 +3409,7 @@ ied)
a touchpad with only two buttons. It is difficult to do a middle
button "paste" because (using XFree86 Emulate3Buttons) you have to
click both buttons on the touch pad at the same time. This remapping:
- [345]-remap Super_R-Button2
+ [343]-remap Super_R-Button2
maps the Super_R "flag" key press to the Button2 click, thereby making
X pasting a bit easier.
@@ -3414,7 +3438,7 @@ ied)
There may also be scaling viewers out there (e.g. TightVNC on Windows)
that automatically shrink or expand the remote framebuffer to fit the
- local display. Especially for hand-held devices. See also [346]this
+ local display. Especially for hand-held devices. See also [344]this
FAQ on x11vnc scaling.
@@ -3423,7 +3447,7 @@ ied)
As of Jun/2004 in the libvncserver CVS x11vnc provides basic
server-side scaling. It is a global scaling of the desktop, not a
- per-client setting. To enable it use the "[347]-scale fraction"
+ per-client setting. To enable it use the "[345]-scale fraction"
option. "fraction" can either be a floating point number (e.g. -scale
0.5) or the alternative m/n fraction notation (e.g. -scale 2/3). Note
that if fraction is greater than one the display is magnified.
@@ -3443,7 +3467,7 @@ ied)
One can also use the ":nb" with an integer scale factor (say "-scale
2:nb") to use x11vnc as a screen magnifier for vision impaired
- [348]applications. Since with integer scale factors the framebuffers
+ [346]applications. Since with integer scale factors the framebuffers
become huge and scaling operations time consuming, be sure to use
":nb" for the fastest response.
@@ -3469,12 +3493,12 @@ ied)
If one desires per-client scaling for something like 1:1 from a
workstation and 1:2 from a smaller device (e.g. handheld), currently
the only option is to run two (or more) x11vnc processes with
- different scalings listening on separate ports ([349]-rfbport option,
+ different scalings listening on separate ports ([347]-rfbport option,
etc.).
As of Mar/2005 in the libvncserver CVS x11vnc now scales the mouse
cursor with the same scale factor as the screen. If you don't want
- that, use the [350]"-scale_cursor frac" option to set the cursor
+ that, use the [348]"-scale_cursor frac" option to set the cursor
scaling to a different factor (e.g. use "-scale_cursor 1" to keep the
cursor at its natural unscaled size).
@@ -3491,16 +3515,16 @@ ied)
rectangular (e.g. 1280x1024 and 1024x768 monitors joined together),
then there will be "non-existent" areas on the screen. The X server
will return "garbage" image data for these areas and so they may be
- distracting to the viewer. The [351]-blackout x11vnc option allows you
+ distracting to the viewer. The [349]-blackout x11vnc option allows you
to blacken-out rectangles by specifying their WxH+X+Y geometries. If
- your system has the libXinerama library, the [352]-xinerama x11vnc
+ your system has the libXinerama library, the [350]-xinerama x11vnc
option can be used to have it automatically determine the rectangles
to be blackened out. (Note on 8bpp PseudoColor displays the fill color
may not be black).
Some users have reported that the mouse does not behave properly for
their Xinerama display: i.e. the mouse cannot be moved to all regions
- of the large display. If this happens try using the [353]-xwarppointer
+ of the large display. If this happens try using the [351]-xwarppointer
option. This instructs x11vnc to fake mouse pointer motions using the
XWarpPointer function instead of the XTestFakeMotionEvent XTEST
function. (This may be due to a bug in the X server for XTEST when
@@ -3525,22 +3549,22 @@ ied)
Note: if you are running on Solaris 8 or earlier you can easily hit up
against the maximum of 6 shm segments per process (for Xsun in this
case) from running multiple x11vnc processes. You should modify
- /etc/system as mentioned in another [354]FAQ to increase the limit. It
- is probably also a good idea to run with the [355]-onetile option in
+ /etc/system as mentioned in another [352]FAQ to increase the limit. It
+ is probably also a good idea to run with the [353]-onetile option in
this case (to limit each x11vnc to 3 shm segments), or even
- [356]-noshm to use no shm segments.
+ [354]-noshm to use no shm segments.
Q-70: Can x11vnc show only a portion of the display? (E.g. for a
special purpose rfb application).
- As of Mar/2005 in the libvncserver CVS x11vnc has the "[357]-clip
+ As of Mar/2005 in the libvncserver CVS x11vnc has the "[355]-clip
WxH+X+Y" option to select a rectangle of width W, height H and offset
(X, Y). Thus the VNC screen will be the clipped sub-region of the
display and be only WxH in size.
This also works to view a sub-region of a single application window if
- the [358]-id or [359]-sid options are used. The offset is measured
+ the [356]-id or [357]-sid options are used. The offset is measured
from the upper left corner of the selected window.
@@ -3549,7 +3573,7 @@ ied)
crash.
As of Dec/2004 in the libvncserver CVS x11vnc supports XRANDR. You
- enable it with the [360]-xrandr option to make x11vnc monitor XRANDR
+ enable it with the [358]-xrandr option to make x11vnc monitor XRANDR
events and also trap X server errors if the screen change occurred in
the middle of an X call like XGetImage. Once it traps the screen
change it will create a new framebuffer using the new screen. If the
@@ -3558,7 +3582,7 @@ ied)
viewer will automatically resize. Otherwise, the new framebuffer is
fit as best as possible into the original viewer size (portions of the
screen may be clipped, unused, etc). For these viewers you can try the
- [361]-padgeom option to make the region big enough to hold all resizes
+ [359]-padgeom option to make the region big enough to hold all resizes
and rotations.
If you specify "-xrandr newfbsize" then vnc viewers that do not
@@ -3612,9 +3636,9 @@ ied)
* Fullscreen mode
The way VMWare does Fullscreen mode on Linux is to display the Guest
- desktop in a separate Virtual Console (e.g. VC 8) (see [362]this FAQ
+ desktop in a separate Virtual Console (e.g. VC 8) (see [360]this FAQ
on VC's for background). Unfortunately, this Fullscreen VC is not an X
- server. So x11vnc cannot access it (however, [363]see this for a
+ server. So x11vnc cannot access it (however, [361]see this for a
possible partial workaround). x11vnc works fine with "Normal X
application window" and "Quick-Switch mode" because these use X.
@@ -3631,13 +3655,13 @@ ied)
response. One can also cut the display depth (e.g. to 16bpp) in this
2nd X session to improve video performance. This 2nd X session
emulates Fullscreen mode to some degree and can be viewed via x11vnc
- as long as the VMWare X session [364]is in the active VC.
+ as long as the VMWare X session [362]is in the active VC.
Also note that with a little bit of playing with "xwininfo -all
-children" output one can extract the (non-toplevel) windowid of the
of the Guest desktop only when VMWare is running as a normal X
application. Then one can export just the guest desktop (i.e. without
- the VMWare menu buttons) by use of the [365]-id windowid option. The
+ the VMWare menu buttons) by use of the [363]-id windowid option. The
caveats are the X session VMWare is in must be in the active VC and
the window must be fully visible, so this mode is not terribly
convenient, but could be useful in some circumstances (e.g. running
@@ -3718,7 +3742,7 @@ ied)
screen to either shm or a mapped file. The format of these is XWD and
so the initial header should be skipped. BTW, since XWD is not
strictly RGB the view will only be approximate. Of course for the case
- of Xvfb x11vnc can poll it much better via the [366]X API, but you get
+ of Xvfb x11vnc can poll it much better via the [364]X API, but you get
the idea.
By default in -rawfb mode x11vnc will actually close any X display it
@@ -3771,7 +3795,7 @@ ied)
keystrokes into the Linux console (e.g. the virtual consoles:
/dev/tty1, /dev/tty2, etc) in x11vnc/misc/vcinject.pl. It is based on
the vncterm/LinuxVNC.c program also in the libvncserver CVS. So to
- view and interact with VC #2 (assuming it is the [367]active VC) one
+ view and interact with VC #2 (assuming it is the [365]active VC) one
can run something like:
x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2'
@@ -3784,7 +3808,7 @@ ied)
more accurate and faster LinuxVNC program. The only advantage x11vnc
-rawfb might have is that it can presumably allow interaction with a
non-text application, e.g. one based on svgalib. For example the
- [368]VMWare Fullscreen mode is actually viewable under -rawfb. But
+ [366]VMWare Fullscreen mode is actually viewable under -rawfb. But
this isn't much use until one figures out how to inject keystrokes and
mouse events.
@@ -3815,9 +3839,9 @@ ied)
As of Jan/2004 in the libvncserver CVS x11vnc supports the "CutText"
part of the rfb protocol. Furthermore, x11vnc is able to hold the
PRIMARY selection (Xvnc does not seem to do this). If you don't want
- the Clipboard/Selection exchanged use the [369]-nosel option. If you
+ the Clipboard/Selection exchanged use the [367]-nosel option. If you
don't want the PRIMARY selection to be polled for changes use the
- [370]-noprimary option.
+ [368]-noprimary option.
You may need to watch out for desktop utilities such as KDE's
"Klipper" that do odd things with the selection, clipboard, and
@@ -3832,7 +3856,7 @@ ied)
not on by default in Solaris, see Xserver(1) for how to turn it on via
+kb), and so you won't hear them if the extension is not present.
- If you don't want to hear the beeps use the [371]-nobell option. If
+ If you don't want to hear the beeps use the [369]-nobell option. If
you want to hear the audio from the remote applications, consider
trying a redirector such as esd.
@@ -3848,7 +3872,7 @@ ied)
Click on the PayPal button below for more info.
Also, in general I always enjoy hearing from x11vnc users, how they
use it, what new features they would like, etc. Please send me an
- [372]email!
+ [370]email!
[PayPal]
@@ -3890,15 +3914,15 @@ References
34. http://sourceforge.net/projects/libvncserver/
35. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=307884
36. http://sourceforge.net/project/shownotes.php?group_id=32584&release_id=307884
- 37. http://www.karlrunge.com/x11vnc/x11vnc.c
- 38. http://www.karlrunge.com/x11vnc/tkx11vnc.h
- 39. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
- 40. http://www.tightvnc.com/download.html
- 41. http://www.realvnc.com/download-free.html
- 42. http://sourceforge.net/projects/cotvnc/
- 43. http://www.karlrunge.com/x11vnc/rx11vnc
- 44. http://www.karlrunge.com/x11vnc/rx11vnc.pl
- 45. http://www.sunfreeware.com/
+ 37. http://www.karlrunge.com/x11vnc/x11vnc-0.7.2.tar.gz
+ 38. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
+ 39. http://www.tightvnc.com/download.html
+ 40. http://www.realvnc.com/download-free.html
+ 41. http://sourceforge.net/projects/cotvnc/
+ 42. http://www.karlrunge.com/x11vnc/rx11vnc
+ 43. http://www.karlrunge.com/x11vnc/rx11vnc.pl
+ 44. http://www.sunfreeware.com/
+ 45. http://www.karlrunge.com/x11vnc/index.html#faq-build
46. ftp://ftp.uu.net/graphics/jpeg/
47. http://www.gzip.org/zlib/
48. http://www.sunfreeware.com/
@@ -4024,208 +4048,206 @@ References
168. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
169. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
170. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
- 171. http://www.karlrunge.com/x11vnc/x11vnc.c
- 172. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sigpipe
- 173. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 174. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
- 175. http://fredrik.hubbe.net/x2vnc.html
- 176. http://www.hubbe.net/~hubbe/win2vnc.html
- 177. http://www.deboer.gmxhome.de/
- 178. http://sourceforge.net/projects/win2vnc/
- 179. http://fredrik.hubbe.net/x2vnc.html
- 180. http://freshmeat.net/projects/x2x/
- 181. http://ftp.digital.com/pub/Digital/SRC/x2x/
- 182. http://zapek.com/software/zvnc/
- 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
- 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
- 186. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
- 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 171. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 172. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
+ 173. http://fredrik.hubbe.net/x2vnc.html
+ 174. http://www.hubbe.net/~hubbe/win2vnc.html
+ 175. http://www.deboer.gmxhome.de/
+ 176. http://sourceforge.net/projects/win2vnc/
+ 177. http://fredrik.hubbe.net/x2vnc.html
+ 178. http://freshmeat.net/projects/x2x/
+ 179. http://ftp.digital.com/pub/Digital/SRC/x2x/
+ 180. http://zapek.com/software/zvnc/
+ 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
+ 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
+ 184. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
+ 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
188. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 190. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 191. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
- 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
- 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
- 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 198. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
- 199. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
- 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
- 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
- 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 211. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 212. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
- 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
- 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
- 219. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 220. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 221. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 223. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 224. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 225. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 189. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 190. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 191. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
+ 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
+ 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 196. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
+ 197. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
+ 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
+ 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 209. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
+ 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
+ 212. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
+ 217. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 218. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 219. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 222. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 223. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
- 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 234. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 235. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 239. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
- 243. ftp://ftp.x.org/
- 244. http://www.karlrunge.com/x11vnc/dtVncPopup
- 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 247. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 250. http://www.karlrunge.com/x11vnc/blockdpy.c
- 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 254. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 255. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 256. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
- 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 258. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
- 259. http://www.jirka.org/gdm-documentation/x241.html
- 260. http://www.karlrunge.com/x11vnc/x11vnc_loop
- 261. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
- 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
- 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 269. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 270. http://www.karlrunge.com/x11vnc/shm_clear
- 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 273. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
- 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 282. http://www.tightvnc.com/
- 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
- 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 232. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 233. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 237. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
+ 241. ftp://ftp.x.org/
+ 242. http://www.karlrunge.com/x11vnc/dtVncPopup
+ 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 245. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 248. http://www.karlrunge.com/x11vnc/blockdpy.c
+ 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 252. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 253. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 254. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
+ 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 256. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
+ 257. http://www.jirka.org/gdm-documentation/x241.html
+ 258. http://www.karlrunge.com/x11vnc/x11vnc_loop
+ 259. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
+ 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
+ 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 267. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 268. http://www.karlrunge.com/x11vnc/shm_clear
+ 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 271. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
+ 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 280. http://www.tightvnc.com/
+ 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
+ 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 297. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 298. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 295. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 296. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
- 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
- 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 308. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
- 309. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
- 310. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
- 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
- 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
- 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
- 316. http://www.tightvnc.com/
- 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
- 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
+ 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
+ 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 306. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
+ 307. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
+ 308. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
+ 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
+ 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
+ 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
+ 314. http://www.tightvnc.com/
+ 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
+ 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
- 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 325. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 326. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 330. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
+ 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 323. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 324. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 328. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
+ 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 341. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 339. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 346. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 348. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
- 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
- 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
- 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
- 354. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
- 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 360. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
- 361. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
+ 344. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 346. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
+ 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 348. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
+ 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
+ 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
+ 352. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 354. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
+ 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
+ 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
+ 360. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 361. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
362. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 363. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
- 364. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 366. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 367. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 368. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
- 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
- 371. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
- 372. mailto:xvml@karlrunge.com
+ 363. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 364. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 365. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 366. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
+ 367. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 368. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
+ 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
+ 370. mailto:xvml@karlrunge.com
=======================================================================
@@ -4238,7 +4260,7 @@ x11vnc: a VNC server for real X displays
Here are all of x11vnc command line options:
% x11vnc -opts (see below for -help long descriptions)
-x11vnc: allow VNC connections to real X11 displays. 0.7.2 lastmod: 2005-05-24
+x11vnc: allow VNC connections to real X11 displays. 0.7.2 lastmod: 2005-05-30
x11vnc options:
-display disp -auth file
@@ -4336,7 +4358,7 @@ libvncserver options:
% x11vnc -help
-x11vnc: allow VNC connections to real X11 displays. 0.7.2 lastmod: 2005-05-24
+x11vnc: allow VNC connections to real X11 displays. 0.7.2 lastmod: 2005-05-30
Typical usage is:
@@ -4495,7 +4517,8 @@ Options:
options apply here as well.
-viewonly All VNC clients can only watch (default off).
--shared VNC display is shared (default off).
+-shared VNC display is shared, i.e. more than one viewer can
+ connect at the same time (default off).
-once Exit after the first successfully connected viewer
disconnects, opposite of -forever. This is the Default.
-forever Keep listening for more connections rather than exiting
@@ -4525,7 +4548,8 @@ Options:
-novncconnect VNC program vncconnect(1). When the property is
set to "host" or "host:port" establish a reverse
connection. Using xprop(1) instead of vncconnect may
- work (see the FAQ). Default: -vncconnect
+ work (see the FAQ). The -remote control mechanism also
+ uses this VNC_CONNECT channel. Default: -vncconnect
-allow host1[,host2..] Only allow client connections from hosts matching
the comma separated list of hostnames or IP addresses.
@@ -5164,7 +5188,8 @@ Options:
Examples: Hitting <Return> in a terminal window when the
cursor was at the bottom, the text scrolls up one line.
Hitting <Down> arrow in a web browser window, the web
- page scrolls up a small amount.
+ page scrolls up a small amount. Or scrolling with a
+ scrollbar or mouse wheel.
Shorter aliases: -scr [mode] and -noscr
@@ -5180,6 +5205,17 @@ Options:
of time. If this is unacceptable disable the feature
with -noscrollcopyrect.
+ Screen clearing kludges: for testing at least, there
+ are some "magic key sequences" (must be done in less
+ than 1 second) to aid repairing painting errors that
+ may be seen when using this mode:
+
+ 3 Alt_L's in a row: resend whole screen,
+ 4 Alt_L's in a row: reread and resend whole screen,
+ 3 Super_L's in a row: mark whole screen for polling,
+ 4 Super_L's in a row: reset RECORD context,
+ 5 Super_L's in a row: try to push a black screen
+
"mode" can be "never" (same as -noscrollcopyrect)
to never try the copyrect, "keys" means to try it
in response to keystrokes only, "mouse" means to
diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1
index acf8a70..c77a708 100644
--- a/x11vnc/x11vnc.1
+++ b/x11vnc/x11vnc.1
@@ -2,7 +2,7 @@
.TH X11VNC "1" "May 2005" "x11vnc " "User Commands"
.SH NAME
x11vnc - allow VNC connections to real X11 displays
- version: 0.7.2, lastmod: 2005-05-24
+ version: 0.7.2, lastmod: 2005-05-30
.SH SYNOPSIS
.B x11vnc
[OPTION]...
@@ -215,7 +215,8 @@ All VNC clients can only watch (default off).
.PP
\fB-shared\fR
.IP
-VNC display is shared (default off).
+VNC display is shared, i.e. more than one viewer can
+connect at the same time (default off).
.PP
\fB-once\fR
.IP
@@ -276,7 +277,8 @@ set to "host" or "host:port" establish a reverse
connection. Using
.IR xprop (1)
instead of vncconnect may
-work (see the FAQ). Default: \fB-vncconnect\fR
+work (see the FAQ). The \fB-remote\fR control mechanism also
+uses this VNC_CONNECT channel. Default: \fB-vncconnect\fR
.PP
\fB-allow\fR \fIhost1[,host2..]\fR
.IP
@@ -1097,7 +1099,8 @@ XCopyArea and XConfigureWindow X protocol requests).
Examples: Hitting <Return> in a terminal window when the
cursor was at the bottom, the text scrolls up one line.
Hitting <Down> arrow in a web browser window, the web
-page scrolls up a small amount.
+page scrolls up a small amount. Or scrolling with a
+scrollbar or mouse wheel.
.IP
Shorter aliases: \fB-scr\fR [mode] and \fB-noscr\fR
.IP
@@ -1113,6 +1116,17 @@ These are automatically repaired in a short period
of time. If this is unacceptable disable the feature
with \fB-noscrollcopyrect.\fR
.IP
+Screen clearing kludges: for testing at least, there
+are some "magic key sequences" (must be done in less
+than 1 second) to aid repairing painting errors that
+may be seen when using this mode:
+.IP
+3 Alt_L's in a row: resend whole screen,
+4 Alt_L's in a row: reread and resend whole screen,
+3 Super_L's in a row: mark whole screen for polling,
+4 Super_L's in a row: reset RECORD context,
+5 Super_L's in a row: try to push a black screen
+.IP
"mode" can be "never" (same as \fB-noscrollcopyrect)\fR
to never try the copyrect, "keys" means to try it
in response to keystrokes only, "mouse" means to
diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c
index be428f8..863d2ea 100644
--- a/x11vnc/x11vnc.c
+++ b/x11vnc/x11vnc.c
@@ -372,7 +372,7 @@ double xdamage_scheduled_mark = 0.0;
sraRegionPtr xdamage_scheduled_mark_region = NULL;
/* date +'lastmod: %Y-%m-%d' */
-char lastmod[] = "0.7.2 lastmod: 2005-05-24";
+char lastmod[] = "0.7.2 lastmod: 2005-05-30";
int hack_val = 0;
/* X display info */
@@ -4232,9 +4232,9 @@ void shutdown_record_context(XRecordContext rc, int bequiet, int reopen) {
}
#endif
-void check_xrecord_reset(void) {
+void check_xrecord_reset(int force) {
static double last_reset = 0.0;
- int reset_time = 120, reset_idle = 15;
+ int reset_time = 90, reset_idle = 10;
int reset_time2 = 600, reset_idle2 = 40;
double now;
XErrorHandler old_handler = NULL;
@@ -4275,13 +4275,13 @@ void check_xrecord_reset(void) {
* try to wait for a break in input to reopen the displays
* this is only to avoid XGrabServer deadlock on the repopens.
*/
- if (now < last_reset + reset_time) {
+ if (force) {
+ ;
+ } else if (now < last_reset + reset_time) {
return;
- }
- if (now < last_pointer_click_time + reset_idle) {
+ } else if (now < last_pointer_click_time + reset_idle) {
return;
- }
- if (now < last_keyboard_time + reset_idle) {
+ } else if (now < last_keyboard_time + reset_idle) {
return;
}
X_LOCK;
@@ -8973,7 +8973,7 @@ void keyboard(rfbBool down, rfbKeySym keysym, rfbClientPtr client) {
char *str;
X_LOCK;
str = XKeysymToString(keysym);
- rfbLog("keyboard(%s, 0x%x \"%s\") %.4f\n", down ? "down":"up",
+ rfbLog("# keyboard(%s, 0x%x \"%s\") %.4f\n", down ? "down":"up",
(int) keysym, str ? str : "null", tnow - x11vnc_start);
X_UNLOCK;
}
@@ -9013,35 +9013,45 @@ void keyboard(rfbBool down, rfbKeySym keysym, rfbClientPtr client) {
key_history[idx].down = down;
key_history[idx].time = tnow;
- if (use_xdamage && down && skip_duplicate_key_events &&
+ if (down && skip_duplicate_key_events &&
(keysym == XK_Alt_L || keysym == XK_Super_L)) {
int i, k, run = 0;
double delay = 1.0;
+ KeySym ks;
for (i=0; i<16; i++) {
k = idx - i;
if (k < 0) k += KEY_HIST;
if (!key_history[k].down) {
continue;
}
+ ks = key_history[k].sym;
if (key_history[k].time < tnow - delay) {
break;
- } else if (key_history[k].sym == XK_Alt_L) {
+ } else if (ks == keysym && ks == XK_Alt_L) {
run++;
- } else if (key_history[k].sym == XK_Super_L) {
+ } else if (ks == keysym && ks == XK_Super_L) {
run++;
} else {
break;
}
}
- if (run == 3) {
- rfbLog("3*Alt_L, calling: set_xdamage_mark()\n");
- set_xdamage_mark(0, 0, dpy_x, dpy_y);
- } else if (run == 4) {
- rfbLog("4*Alt_L, calling: refresh_screen(0)\n");
+ if (run == 3 && keysym == XK_Alt_L) {
+ rfbLog("3*Alt_L, calling: refresh_screen(0)\n");
refresh_screen(0);
- } else if (run == 5) {
- rfbLog("5*Alt_L, setting: do_copy_screen\n");
+ } else if (run == 4 && keysym == XK_Alt_L) {
+ rfbLog("4*Alt_L, setting: do_copy_screen\n");
do_copy_screen = 1;
+ } else if (run == 5 && keysym == XK_Alt_L) {
+ ;
+ } else if (run == 3 && keysym == XK_Super_L) {
+ rfbLog("3*Super_L, calling: set_xdamage_mark()\n");
+ set_xdamage_mark(0, 0, dpy_x, dpy_y);
+ } else if (run == 4 && keysym == XK_Super_L) {
+ rfbLog("4*Super_L, calling: check_xrecord_reset()\n");
+ check_xrecord_reset(1);
+ } else if (run == 5 && keysym == XK_Super_L) {
+ rfbLog("5*Super_L, calling: push_black_screen(0)\n");
+ push_black_screen(0);
}
}
@@ -9897,7 +9907,7 @@ void pointer(int mask, int x, int y, rfbClientPtr client) {
dt = tnow - last_pointer;
last_pointer = tnow;
if (show_motion) {
- rfbLog("pointer(mask: 0x%x, x:%4d, y:%4d) "
+ rfbLog("# pointer(mask: 0x%x, x:%4d, y:%4d) "
"dx: %3d dy: %3d dt: %.4f t: %.4f\n", mask, x, y,
x - last_x, y - last_y, dt, tnow);
}
@@ -25465,7 +25475,7 @@ if (db2) fprintf(stderr, " stack_work dt: %.4f\n", dt);
dtime0(&tm);
do_copyregion(shifted_region, dx, dy);
dt = dtime(&tm);
-if (db2) fprintf(stderr, "do_copyregion: %d %d %d %d dx: %d dy: %d dt: %.4f\n",
+if (0 || db2) fprintf(stderr, "do_copyregion: %d %d %d %d dx: %d dy: %d dt: %.4f\n",
tx1, ty1, tx2, ty2, dx, dy, dt);
sent_copyrect = 1;
}
@@ -27470,7 +27480,7 @@ if (debug_scroll) fprintf(stderr, "watch_loop: LOOP-BACK: %d\n", ret);
check_connect_inputs();
check_padded_fb();
check_xdamage_state();
- check_xrecord_reset();
+ check_xrecord_reset(0);
check_add_keysyms();
if (started_as_root) {
check_switched_user();
@@ -27732,7 +27742,8 @@ static void print_help(int mode) {
" options apply here as well.\n"
"\n"
"-viewonly All VNC clients can only watch (default %s).\n"
-"-shared VNC display is shared (default %s).\n"
+"-shared VNC display is shared, i.e. more than one viewer can\n"
+" connect at the same time (default %s).\n"
"-once Exit after the first successfully connected viewer\n"
" disconnects, opposite of -forever. This is the Default.\n"
"-forever Keep listening for more connections rather than exiting\n"
@@ -27762,7 +27773,8 @@ static void print_help(int mode) {
"-novncconnect VNC program vncconnect(1). When the property is\n"
" set to \"host\" or \"host:port\" establish a reverse\n"
" connection. Using xprop(1) instead of vncconnect may\n"
-" work (see the FAQ). Default: %s\n"
+" work (see the FAQ). The -remote control mechanism also\n"
+" uses this VNC_CONNECT channel. Default: %s\n"
"\n"
"-allow host1[,host2..] Only allow client connections from hosts matching\n"
" the comma separated list of hostnames or IP addresses.\n"
@@ -28413,7 +28425,8 @@ static void print_help(int mode) {
" Examples: Hitting <Return> in a terminal window when the\n"
" cursor was at the bottom, the text scrolls up one line.\n"
" Hitting <Down> arrow in a web browser window, the web\n"
-" page scrolls up a small amount.\n"
+" page scrolls up a small amount. Or scrolling with a\n"
+" scrollbar or mouse wheel.\n"
"\n"
" Shorter aliases: -scr [mode] and -noscr\n"
"\n"
@@ -28429,6 +28442,17 @@ static void print_help(int mode) {
" of time. If this is unacceptable disable the feature\n"
" with -noscrollcopyrect.\n"
"\n"
+" Screen clearing kludges: for testing at least, there\n"
+" are some \"magic key sequences\" (must be done in less\n"
+" than 1 second) to aid repairing painting errors that\n"
+" may be seen when using this mode:\n"
+"\n"
+" 3 Alt_L's in a row: resend whole screen,\n"
+" 4 Alt_L's in a row: reread and resend whole screen,\n"
+" 3 Super_L's in a row: mark whole screen for polling,\n"
+" 4 Super_L's in a row: reset RECORD context,\n"
+" 5 Super_L's in a row: try to push a black screen\n"
+"\n"
" \"mode\" can be \"never\" (same as -noscrollcopyrect)\n"
" to never try the copyrect, \"keys\" means to try it\n"
" in response to keystrokes only, \"mouse\" means to\n"
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-26 20:27:41 +0000