summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--x11vnc/ChangeLog3
-rw-r--r--x11vnc/README934
-rw-r--r--x11vnc/help.c19
-rw-r--r--x11vnc/x11vnc.119
-rw-r--r--x11vnc/x11vnc.h2
5 files changed, 504 insertions, 473 deletions
diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog
index 9b9f3c1..d6343ed 100644
--- a/x11vnc/ChangeLog
+++ b/x11vnc/ChangeLog
@@ -1,4 +1,7 @@
2006-02-06 Karl Runge <runge@karlrunge.com>
+ * x11vnc: fix AIX build wrt h_errno.
+
+2006-02-06 Karl Runge <runge@karlrunge.com>
* x11vnc: -8to24 more speedups; tunables for very slow machines.
2006-02-04 Karl Runge <runge@karlrunge.com>
diff --git a/x11vnc/README b/x11vnc/README
index 299e0fc..7f40425 100644
--- a/x11vnc/README
+++ b/x11vnc/README
@@ -1,5 +1,5 @@
-x11vnc README file Date: Mon Feb 6 00:16:18 EST 2006
+x11vnc README file Date: Mon Feb 6 12:56:16 EST 2006
The following information is taken from these URLs:
@@ -1636,18 +1636,18 @@ display :0
You may want to review the [212]previous question regarding 8 bpp
PseudoColor.
- On some hardware (Sun/SPARC, Sgi), the [213]-overlay option discussed
- a couple paragraphs down may solve this for you (you may want to skip
- to it directly). On other hardware the less robust [214]-8to24 option
- may help.
+ On some hardware (Sun/SPARC and SGI), the [213]-overlay option
+ discussed a couple paragraphs down may solve this for you (you may
+ want to skip to it directly). On other hardware the less robust
+ [214]-8to24 option may help (also discussed below).
Run xdpyinfo(1) to see what the default visual is and what the depths
- of the other visuals are. Does the default visual have a depth of 8?
- If it does, can you possibly re-configure your X server to make the
- depth 24 visual the default? If you can do it, this will save you a
- lot of grief WRT colors and x11vnc (and for general usage too!). Here
- is how I do this on an old Sparcstation 20 running Solaris 9 with SX
- graphics
+ of the other visuals are. Does the default visual have a depth of 8
+ but there are other visuals of depth 24? If it does, can you possibly
+ re-configure your X server to make a depth 24 visual the default? If
+ you can do it, this will save you a lot of grief WRT colors and x11vnc
+ (and for general usage too!). Here is how I do this on an old
+ Sparcstation 20 running Solaris 9 with SX graphics
xinit -- -dev /dev/fb defclass TrueColor defdepth 24
and it works nicely (note: to log into console from the dtlogin
@@ -1674,7 +1674,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
+ visuals is a Sun system running Solaris or SGI running IRIX you can
use the [215]-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
@@ -1684,6 +1684,12 @@ TrueColor defdepth 24
24 visuals are available, and so the default depth workaround
described in the previous paragraph is not sufficient for these apps.
+ It seems that Xorg is working toward supporting XReadDisplay(3X11) as
+ part of the RENDER extension work. When it does support it and
+ provides a library API x11vnc will be modified to take advantage of
+ the feature to support -overlay on Linux, *BSD, etc. Until then see
+ the -8to24 mode below.
+
Misc. notes on -overlay mode: An amusing by-product of -overlay mode
is that the mouse cursor shape is correct! (i.e. XFIXES is not
needed). The -overlay mode may be somewhat slower than normal mode due
@@ -1696,45 +1702,53 @@ TrueColor defdepth 24
The -8to24 mode: The [216]-8to24 x11vnc option (Jan/2006) is a kludge
to try to dynamically rewrite the pixel values so that the 8bpp part
- is mapped onto depth 24 TrueColor and overwrites bits 1-24 of the
- pixel. This is less robust than the -overlay mode because it is done
- by x11vnc outside of the X server. So only use it on OS's that do not
- support -overlay. The -8to24 mode will work if the default visual is
- depth 24. Then it scans for any windows within 3 levels of the root
- window that are 8bpp (i.e. legacy application). For the ones it finds
- it tries to use the correct indexed colormap to rewrite bits 1-24 of
- the pixels. (Update: it now also works to some degree with default
- visual depth 8 and depth 24 windows on the screen, updates may be
- missed however).
+ of the screen is mapped onto depth 24 TrueColor. This is less robust
+ than the -overlay mode because it is done by x11vnc outside of the X
+ server. So only use it on OS's that do not support -overlay. The
+ -8to24 mode will work if the default visual is depth 24 or depth 8. It
+ scans for any windows within 3 levels of the root window that are 8bpp
+ (i.e. legacy application), or in general ones that are not using the
+ default visual. For the windows it finds it uses XGetSubImage() to
+ retrieve the pixels values and uses the correct indexed colormap to
+ create a depth 24 TrueColor view of the whole screen. This depth 24,
+ 32bpp view is exported via VNC.
+
+ Even on pure 8bpp displays it can be used as an alternative to
+ [217]-flashcmap to avoid color flashing completely.
This scheme is approximate and can often lead to painting errors. You
can manually correct most painting errors by pressing 3 Alt_L's in a
- row, or by using something like: [217]-fixscreen V=3.0 to
- automatically refresh the screen every 3 seconds. In general the
- scheme uses many resources and may give rise to sluggish behavior. If
- multiple windows are using different 8bpp indexed colormaps all but
- one window may need to be iconified for the colors to be correct.
-
- If there are problems with this mode you can try a different version
- of it by setting the XGETIMAGE_8TO24 environment variable to any
- string (e.g. "1"). This will use XGetImage() instead of stripping out
- bits 25-32. This will be slower.
+ row, or by using something like: [218]-fixscreen V=3.0 to
+ automatically refresh the screen every 3 seconds. Also -fixscreen
+ 8=3.0 has been added to just refresh the non-default visual parts of
+ the screen.
+
+ In general the scheme uses many resources and may give rise to
+ sluggish behavior. If multiple windows are using different 8bpp
+ indexed colormaps all but one window may need to be iconified for the
+ colors to be correct. There are a number of tunable parameters to try
+ to adjust performance and painting accuracy. The option -8to24
+ nogetimage can give a nice speedup if the default depth 24 X server
+ supports hiding the 8bpp bits in bits 25-32 of the framebuffer data.
+ On very slow machines -8to24 poll=0.2,cachewin=5.0 gives an useful
+ speedup. See the [219]-8to24 help description for information on
+ tunable parameters, etc.
Colors still not working correctly? Run xwininfo on the application
with the incorrect 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 [218]-id option to
+ possible workaround in this case is to use the [220]-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).
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. The [219]-8to24 method
- does this approximately. Fortunately the [220]-overlay option works
- for Solaris machines with overlay visuals where most of this problem
- occurs.
+ for x11vnc to be able to do so in real time. The [221]-8to24 method
+ does this approximately and is somewhat usable. Fortunately the
+ [222]-overlay option works for Solaris machines with overlay visuals
+ where most of this problem occurs.
Q-17: How do I figure out the window id to supply to the -id windowid
@@ -1744,9 +1758,9 @@ 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 [221]color problems.
+ debugging x11vnc [223]color problems.
- Also, as of Dec/2004 libvncserver CVS you can use "[222]-id pick" to
+ Also, as of Dec/2004 libvncserver CVS you can use "[224]-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.
@@ -1764,7 +1778,7 @@ TrueColor defdepth 24
you should be able to see these transient windows.
If things are not working and you still want to do the single window
- polling, try the [223]-sid windowid option ("shifted" windowid).
+ polling, try the [225]-sid windowid option ("shifted" windowid).
Q-19: My X display is depth 24 at 24bpp (instead of the normal depth
@@ -1814,15 +1828,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 [224]-display option to point the display to that of
+ machine. Use the [226]-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 [225]-noshm option (this enables the polling over
+ and also supply the [227]-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 [226]-flipbyteorder if the
+ on the polling rate. You may also need [228]-flipbyteorder if the
colors get messed up due to endian byte order differences.
Q-21: How do I get my X permissions (MIT-MAGIC-COOKIE file) correct
@@ -1846,7 +1860,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
- [227]-auth option to point to the correct file). Other options include
+ [229]-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 -
@@ -1858,7 +1872,7 @@ TrueColor defdepth 24
details.
If the display name in the cookie file needs to be changed between the
- two hosts, see [228]this note on the "xauth add ..." command.
+ two hosts, see [230]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
@@ -1872,7 +1886,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 [229]poll
+ Not recommended, but as a last resort, you could have x11vnc [231]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...)
@@ -1903,17 +1917,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
- [230]-remote and [231]-query options. To shut down the running x11vnc
+ [232]-remote and [233]-query options. To shut down the running x11vnc
server just type "x11vnc -R stop". To disconnect all clients do
"x11vnc -R disconnect:all", etc.
- If the [232]-forever option has not been supplied, x11vnc will
+ If the [234]-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 [233]-bg option
+ If you have not put x11vnc in the background via the [235]-bg option
or shell & operator, then simply press Ctrl-C in the shell where
x11vnc is running to stop it.
@@ -1923,15 +1937,15 @@ TrueColor defdepth 24
down state in the Xserver. 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 [234]-clear_mods
- option and [235]-clear_keys option can be used to release pressed keys
+ by tapping Ctrl, Shift, and Alt. Alternatively, the [236]-clear_mods
+ option and [237]-clear_keys option can be used to release pressed keys
at startup and exit.
Q-23: Can I change settings in x11vnc without having to restart it?
Can I remote control it?
- Look at the [236]-remote (same as -R) and [237]-query (same as -Q)
+ Look at the [238]-remote (same as -R) and [239]-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
@@ -1943,7 +1957,7 @@ TrueColor defdepth 24
be possible.
There is also a simple Tcl/Tk gui based on this remote control
- mechanism. See the [238]-gui option for more info. You will need to
+ mechanism. See the [240]-gui option for more info. You will need to
have Tcl/Tk (i.e. /usr/bin/wish) installed for it to work. It can also
run in the system tray: "-gui tray" or as a standalone icon window:
"-gui icon".
@@ -1958,12 +1972,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" [239]option, which is the the same
+ the -storepasswd "pass" "file" [241]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: [240]-rfbauth
+ You then use the password via the x11vnc option: [242]-rfbauth
$HOME/myvncpasswd
Compared to vncpasswd(1) the latter two methods are a somewhat unsafe
@@ -1972,7 +1986,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 [241]-passwdfile and -passwd/-viewpasswd plain
+ x11vnc also has the [243]-passwdfile and -passwd/-viewpasswd plain
text (i.e. not obscured like the -rfbauth VNC passwords) password
options.
@@ -1983,7 +1997,7 @@ TrueColor defdepth 24
You can use the vncpasswd program from RealVNC or TightVNC mentioned
above..
- Alternatively, this script should keep your [242]-storepasswd more
+ Alternatively, this script should keep your [244]-storepasswd more
private:
#!/bin/sh
# usage: x11vnc_pw [file] (default: ~/.vnc/passwd)
@@ -2018,13 +2032,13 @@ ls -l "$file"
and the other for view-only access to the display?
Yes, as of May/2004 in the libvncserver CVS there is the
- [243]-viewpasswd option to supply the view-only password. Note the
- full-access password option [244]-passwd must be supplied at the same
+ [245]-viewpasswd option to supply the view-only password. Note the
+ full-access password option [246]-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
- [245]-passwdfile option to specify a file containing plain text
+ [247]-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
@@ -2032,7 +2046,7 @@ ls -l "$file"
it is taken as the view-only password. (use "__EMPTY__" to supply an
empty one).
- View-only passwords currently do not work for the [246]-rfbauth
+ View-only passwords currently do not work for the [248]-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
@@ -2045,7 +2059,7 @@ ls -l "$file"
Q-27: Can I have as many full-access and view-only passwords as I
like?
- Yes, as of Jan/2006 in the libvncserver CVS the [247]-passwdfile
+ Yes, as of Jan/2006 in the libvncserver CVS the [249]-passwdfile
option has been extended to handle as many passwords as you like. You
put the view-only passwords after a line __BEGIN_VIEWONLY__.
@@ -2057,7 +2071,7 @@ ls -l "$file"
some users just be able to move the mouse, but not click or type
anything?
- As of Feb/2005, the [248]-input option allows you to do this. "K",
+ As of Feb/2005, the [250]-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
@@ -2073,15 +2087,15 @@ ls -l "$file"
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 [249]-forever option (aka -many) to have
+ periods of time. Use the [251]-forever option (aka -many) to have
x11vnc wait for more connections after the first client disconnects.
- Use the [250]-shared option to have x11vnc allow multiple clients to
+ Use the [252]-shared option to have x11vnc allow multiple clients to
connect simultaneously.
- Recommended additional safety measures include using ssh ([251]see
+ Recommended additional safety measures include using ssh ([253]see
above), stunnel, or a VPN to authenticate and encrypt the viewer
- connections or to at least use the -rfbauth passwd-file [252]option to
- use VNC password protection (or [253]-passwdfile) It is up to YOU to
+ connections or to at least use the -rfbauth passwd-file [254]option to
+ use VNC password protection (or [255]-passwdfile) It is up to YOU to
apply these security measures, they will not be done for you
automatically.
@@ -2089,7 +2103,7 @@ ls -l "$file"
Q-30: Can I limit which machines incoming VNC clients can connect
from?
- Yes, look at the [254]-allow and [255]-localhost options to limit
+ Yes, look at the [256]-allow and [257]-localhost options to limit
connections by hostname or IP address. E.g.
x11vnc -allow 192.168.0.1,192.168.0.2
@@ -2101,7 +2115,7 @@ ls -l "$file"
Note that -localhost is the same as "-allow 127.0.0.1"
For more control, build libvncserver with libwrap support
- [256](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
+ [258](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
for complete details.
@@ -2121,7 +2135,7 @@ ls -l "$file"
is "vnc", e.g.:
vnc: 192.168.100.3 .example.com
- Note that if you run x11vnc out of [257]inetd you do not need to build
+ Note that if you run x11vnc out of [259]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.
@@ -2130,16 +2144,16 @@ ls -l "$file"
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 "[258]-listen
+ As of Mar/2005 in the libvncserver CVS, there is the "[260]-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 "[259]-allow host1,..." option to allow only specific hosts
+ use the "[261]-allow host1,..." option to allow only specific hosts
in.
This option is useful if you want to insure that no one can even begin
a dialog with x11vnc from untrusted network interfaces (e.g. ppp0).
- The option [260]-localhost now implies "-listen localhost" since that
+ The option [262]-localhost now implies "-listen localhost" since that
is what most people expect it to do.
@@ -2147,24 +2161,24 @@ ls -l "$file"
interface, how I can occasionally allow in a non-localhost via the -R
allowonce remote control command?
- To do this specify "[261]-allow localhost". Unlike [262]-localhost
+ To do this specify "[263]-allow localhost". Unlike [264]-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
- ([263]-listen option) via remote control or gui, you may need to also
- manually adjust the [264]-allow list if you unexpectedly get into a
+ ([265]-listen option) via remote control or gui, you may need to also
+ manually adjust the [266]-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 [265]-localhost on
+ in on the listening interface. If you just toggle [267]-localhost on
and off x11vnc should see to it that you never get into such a state.
Q-34: 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 [266]how to tunnel VNC via
+ See the description earlier on this page on [268]how to tunnel VNC via
SSH from Unix to Unix. A number of ways are described along with some
issues you may encounter.
@@ -2175,7 +2189,7 @@ ls -l "$file"
Q-35: How can I tunnel my connection to x11vnc via an encrypted SSH
channel from Windows using an SSH client like Putty?
- [267]Above we described how to tunnel VNC via SSH from Unix to Unix,
+ [269]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
@@ -2198,8 +2212,8 @@ ls -l "$file"
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 [268]-localhost
- and [269]-rfbauth/[270]-passwdfile options.
+ For extra protection feel free to run x11vnc with the [270]-localhost
+ and [271]-rfbauth/[272]-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
@@ -2207,11 +2221,11 @@ ls -l "$file"
dialog setting to: 'Destination: otherhost:5900', Once logged in,
you'll need to do a second login (ssh or rsh) to the workstation
machine 'otherhost' and then start up x11vnc on it. This can also be
- automated by [271]chaining ssh's.
+ automated by [273]chaining ssh's.
- As discussed [272]above another option is to first start the VNC
+ As discussed [274]above another option is to first start the VNC
viewer in "listen" mode, and then launch x11vnc with the
- "[273]-connect localhost" option to establish the reverse connection.
+ "[275]-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).
@@ -2222,7 +2236,7 @@ ls -l "$file"
some clients view-only? How about running an arbitrary program to make
the decisions?
- Yes, look at the "[274]-accept command" option, it allows you to
+ Yes, look at the "[276]-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
@@ -2241,7 +2255,7 @@ ls -l "$file"
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 [275]-viewonly option has been
+ mouse on the "View" button. If the [277]-viewonly option has been
supplied, the "View" action will not be present: the whole display is
view only in that case.
@@ -2257,7 +2271,7 @@ ls -l "$file"
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 [276]ftp://ftp.x.org/
+ is available at [278]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
@@ -2296,7 +2310,7 @@ elif [ $rc = 4 ]; then
fi
exit 1
- Stefan Radman has written a nice dtksh script [277]dtVncPopup for use
+ Stefan Radman has written a nice dtksh script [279]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.
@@ -2305,7 +2319,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 "[278]-gone
+ To run a command when a client disconnects, use the "[280]-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
@@ -2320,13 +2334,13 @@ exit 1
such support.
One approximate method involves starting x11vnc with the
- [279]-localhost option. This basically requires the viewer user to log
+ [281]-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 [280]elsewhere on this page. Of course a malicious user
+ mentioned [282]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
@@ -2335,7 +2349,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 [281]-accept option that runs a program to examine
+ involves using the [283]-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
@@ -2368,7 +2382,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 [282]-users option that allows things
+ As of Feb/2005 x11vnc has the [284]-users option that allows things
like this. Please read the documentation on it (also in the x11vnc
-help output) carefully for features and caveats. It's use can often
decrease security unless care is taken.
@@ -2390,7 +2404,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 [283]blockdpy.c The idea behind it is simple (but
+ source for it is [285]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
@@ -2406,8 +2420,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 [284]-accept option and told
- to exit via the [285]-gone option (the vnc client user should
+ The blockdpy utility is launched by the [286]-accept option and told
+ to exit via the [287]-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.
@@ -2415,7 +2429,7 @@ exit 1 # reject it
Q-40: Can I have x11vnc automatically lock the screen when I
disconnect the VNC viewer?
- Yes, a user mentions he uses the [286]-gone option under CDE to run a
+ Yes, a user mentions he uses the [288]-gone option under CDE to run a
screen lock program:
x11vnc -display :0 -forever -gone 'dtaction LockDisplay'
@@ -2424,7 +2438,7 @@ exit 1 # reject it
x11vnc -display :0 -forever -gone 'kdesktop_lock'
x11vnc -display :0 -forever -gone 'xlock &'
- Here is a scheme using the [287]-afteraccept option (in version 0.7.3)
+ Here is a scheme using the [289]-afteraccept option (in version 0.7.3)
to unlock the screen after the first valid VNC login and to lock the
screen after the last valid VNC login disconnects:
x11vnc -display :0 -forever -shared -afteraccept ./myxlocker -gone ./myxlocke
@@ -2463,11 +2477,11 @@ fi
need to have sufficient permissions to connect to the X display.
Here are some ideas:
- * Use the description under "Continuously" in the [288]FAQ on x11vnc
+ * Use the description under "Continuously" in the [290]FAQ on x11vnc
and Display Managers
- * Use the description in the [289]FAQ on x11vnc and inetd(1)
+ * Use the description in the [291]FAQ on x11vnc and inetd(1)
* Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc)
- * Although less reliable, see the [290]x11vnc_loop rc.local hack
+ * Although less reliable, see the [292]x11vnc_loop rc.local hack
below.
The display manager scheme will not be specific to which user has the
@@ -2498,7 +2512,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 [291]-auth option sets the XAUTHORITY variable for you).
+ (the [293]-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
@@ -2523,7 +2537,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
- [292]the example at the end of this FAQ). Then restart dtlogin, e.g.:
+ [294]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
@@ -2586,7 +2600,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 [293]full details
+ killed immediately after the user logs in. Here are [295]full details
on how to configure gdm
_________________________________________________________________
@@ -2628,13 +2642,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: [294]x11vnc_loop It will need some local
+ file like rc.local: [296]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
- [295]this FAQ.
+ [297]this FAQ.
Q-43: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
@@ -2644,7 +2658,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 [296]-inetd
+ where the shell script /usr/local/bin/x11vnc_sh uses the [298]-inetd
option and looks something like (you'll need to customize to your
settings).
#!/bin/sh
@@ -2657,7 +2671,7 @@ rever -bg
and that confuses it greatly, causing it to abort). 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 [297]-quiet) option: "/usr/local/bin/x11vnc -q
+ specify the -q (aka [299]-quiet) option: "/usr/local/bin/x11vnc -q
-inetd ...". When you supply both -q and -inet and no "-o logfile"
then stderr will automatically be closed (to prevent, e.g. library
stderr messages leaking out to the viewer). The recommended practice
@@ -2665,7 +2679,7 @@ rever -bg
script with "2>logfile" redirection because the errors and warnings
printed out are very useful in troubleshooting problems.
- Note also the need to set XAUTHORITY via [298]-auth to point to the
+ Note also the need to set XAUTHORITY via [300]-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
@@ -2732,7 +2746,7 @@ service x11vncservice
Q-44: Can I have x11vnc restart itself after it terminates?
One could do this in a shell script, but now there is an option
- [299]-loop that makes it easier. Of course when x11vnc restarts it
+ [301]-loop that makes it easier. Of course when x11vnc restarts it
needs to have permissions to connect to the (potentially new) X
display. This mode could be useful if the X server restarts often. Use
e.g. "-loop5000" to sleep 5000 ms between restarts. Also "-loop2000,5"
@@ -2743,7 +2757,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 [300]option:
+ that connect to it, run x11vnc with this [302]option:
-httpdir /path/to/the/java/classes/dir
(this directory will contain the files index.vnc and, for example,
@@ -2762,7 +2776,7 @@ service x11vncservice
then you can connect to that URL with any Java enabled browser. Feel
free to customize the default index.vnc file in the classes directory.
- As of May/2005 the [301]-http option will try to guess where the Java
+ As of May/2005 the [303]-http option will try to guess where the Java
classes jar file is by looking a expected locations.
Also note that if you wanted to, you could also start the Java viewer
@@ -2776,7 +2790,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 [302]-connect option. To connect immediately
+ starts up x11vnc with the [304]-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
@@ -2784,7 +2798,7 @@ service x11vncservice
hosts to connect to.
To use the vncconnect(1) program (from the core VNC package at
- www.realvnc.com) specify the [303]-vncconnect option to x11vnc (Note:
+ www.realvnc.com) specify the [305]-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
@@ -2828,7 +2842,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
- [304]-add_keysyms option to have keysyms added automatically. Also, to
+ [306]-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"
@@ -2850,11 +2864,11 @@ xmodmap -e "add Control = Control_L Control_R"
The main drawback to this method (besides requiring extra
configuration and possibly root permission) is that it also does the
- Linux Virtual Console/Terminal (VC/VT) [305]switching even though it
+ Linux Virtual Console/Terminal (VC/VT) [307]switching even though it
does not need to (since it doesn't use a real framebuffer). There are
some "dual headed" (actually multi-headed/multi-user) patches to the X
server that turn off the VT usage in the X server. Update: As of
- Jul/2005 we have an LD_PRELOAD script [306]Xdummy that allows you to
+ Jul/2005 we have an LD_PRELOAD script [308]Xdummy that allows you to
use a stock (i.e. unpatched) Xorg or XFree86 server with the "dummy"
driver and not have any VT switching problems! Currently Xdummy needs
to be run as root, but with some luck that may be relaxed in the
@@ -2886,7 +2900,7 @@ startx -- /path/to/Xdummy :1
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 [307]this FAQ) and access it from
+ display via x11vnc (e.g. see [309]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
@@ -2929,7 +2943,7 @@ startx -- /path/to/Xdummy :1
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 [308]shm_clear to list and prompt for removal
+ Here is a shell script [310]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,
@@ -2963,36 +2977,36 @@ ied)
in /etc/system. See the next paragraph for more workarounds.
To minimize the number of shm segments used by x11vnc try using the
- [309]-onetile option (corresponds to only 3 shm segments used, and
+ [311]-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
- [310]-noshm option. Performance will be somewhat degraded but when
+ [312]-noshm option. Performance will be somewhat degraded but when
done over local machine sockets it should be acceptable (see an
- [311]earlier question discussing -noshm).
+ [313]earlier question discussing -noshm).
Q-50: How can I make x11vnc use less system resources?
- The [312]-nap and "[313]-wait n" (where n is the sleep between polls
+ The [314]-nap and "[315]-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. The
ShadowFB will make x11vnc's screen polling less severe. Using the
- [314]-onetile option will use less memory and use fewer shared memory
- slots (add [315]-fs 1.0 for one less slot).
+ [316]-onetile option will use less memory and use fewer shared memory
+ slots (add [317]-fs 1.0 for one less slot).
Q-51: How can I make x11vnc use MORE system resources?
- You can try [316]-threads and dial down the wait time (e.g. -wait 1)
- and possibly dial down [317]-defer as well. Note that if you try to
+ You can try [318]-threads and dial down the wait time (e.g. -wait 1)
+ and possibly dial down [319]-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 [318]-id option) can be streamed over a LAN or wireless at
+ the x11vnc [320]-id option) can be streamed over a LAN or wireless at
a reasonable frame rate.
@@ -3008,16 +3022,16 @@ 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
- [319]-solid [color] option to try to do this automatically.
+ [321]-solid [color] option to try to do this automatically.
* Configure your window manager or desktop "theme" to not use fancy
images, shading, and gradients for the window decorations, etc.
Disable window animations, etc. Maybe your desktop has a "low
bandwidth" theme you can easily switch into and out of.
* Avoid small scrolls of large windows using the Arrow keys or
scrollbar. Try to use PageUp/PageDown instead. (not so much of a
- problem in x11vnc 0.7.2 if [320]-scrollcopyrect is active and
+ problem in x11vnc 0.7.2 if [322]-scrollcopyrect is active and
detecting scrolls for the application).
- * If the [321]-wireframe option is not available (earlier than
+ * If the [323]-wireframe option is not available (earlier than
x11vnc 0.7.2 or you have disabled it via -nowireframe) then
Disable Opaque Moves and Resizes in the window manager/desktop.
* However if -wireframe is active (on by default in x11vnc 0.7.2)
@@ -3037,7 +3051,7 @@ ied)
noticed.
VNC viewer parameters:
- * Use a [322]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer
+ * Use a [324]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer
with ZRLE encoding is not too bad either; some claim it is
faster).
* Make sure the tight (or zrle) encoding is being used (look at
@@ -3060,28 +3074,28 @@ ied)
file.
x11vnc parameters:
- * Try using [323]-nodragging (no screen updates when dragging mouse,
+ * Try using [325]-nodragging (no screen updates when dragging mouse,
but sometimes you miss visual feedback)
- * Make sure the [324]-wireframe option is active (it should be on by
+ * Make sure the [326]-wireframe option is active (it should be on by
default) and you have Opaque Moves/Resizes Enabled in the window
manager.
- * Make sure the [325]-scrollcopyrect option is active (it should be
+ * Make sure the [327]-scrollcopyrect option is active (it should be
on by default). This detects scrolls in many (but not all)
applications an applies the CopyRect encoding for a big speedup.
- * Set [326]-fs 1.0 (disables fullscreen updates)
- * Try increasing [327]-wait or [328]-defer (reduces the maximum
+ * Set [328]-fs 1.0 (disables fullscreen updates)
+ * Try increasing [329]-wait or [330]-defer (reduces the maximum
"frame rate", but won't help much for large screen changes)
- * Try the [329]-progressive pixelheight mode with the block
+ * Try the [331]-progressive pixelheight mode with the block
pixelheight 100 or so (delays sending vertical blocks since they
may change while viewer is receiving earlier ones)
- * If you just want to watch one (simple) window use [330]-id (cuts
+ * If you just want to watch one (simple) window use [332]-id (cuts
down extraneous polling and updates, but can be buggy or
insufficient)
- * Set [331]-nosel (disables all clipboard selection exchange)
- * Use [332]-nocursor and [333]-nocursorpos (repainting the remote
+ * Set [333]-nosel (disables all clipboard selection exchange)
+ * Use [334]-nocursor and [335]-nocursorpos (repainting the remote
cursor position and shape takes resources and round trips)
* On very slow links (e.g. <= 28.8) you may need to increase the
- [334]-readtimeout n setting if it sometimes takes more than 20sec
+ [336]-readtimeout n setting if it sometimes takes more than 20sec
to paint the full screen, etc.
@@ -3103,7 +3117,7 @@ ied)
Note that the DAMAGE extension does not speed up the actual reading of
pixels from the video card framebuffer memory, by, say, mirroring them
- in main memory. So reading the fb is still painfully [335]slow (e.g.
+ in main memory. So reading the fb is still painfully [337]slow (e.g.
5MB/sec), and so even using X DAMAGE when large changes occur on the
screen the bulk of the time is still spent retrieving them. Not ideal,
but use of the ShadowFB XFree86/Xorg option speeds up the reading
@@ -3121,27 +3135,27 @@ 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 "[336]-xd_area A" option to adjust the size
+ skipped). You can use the "[338]-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 "[337]-xd_mem f" may also be of use in tuning the
- algorithm. To disable using DAMAGE entirely use "[338]-noxdamage".
+ The option "[339]-xd_mem f" may also be of use in tuning the
+ algorithm. To disable using DAMAGE entirely use "[340]-noxdamage".
Q-54: When I drag windows around with the mouse or scroll up and down
things really bog down (unless I do the drag in a single, quick
motion). Is there anything to do to improve things?
- This problem is primarily due to [339]slow hardware read rates from
+ This problem is primarily due to [341]slow hardware read rates from
video cards: as you scroll or move a large window around the screen
changes are much too rapid for x11vnc to keep up them (it can usually
only read the video card at about 5-10 MB/sec, so it can take a good
fraction of a 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
- [340]-pointer_mode option for more info. The next bottleneck is
+ [342]-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
@@ -3151,26 +3165,26 @@ 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 "[341]-pointer_mode 1" option.
+ way via the "[343]-pointer_mode 1" option.
- Also added was the [342]-nodragging option that disables all screen
+ Also added was the [344]-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 [343]-pointer_mode n option
+ As of Dec/2004 in the libvncserver CVS the [345]-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 [344]-threads option can improve
+ Also, in some circumstances the [346]-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).
As of Apr/2005 in the libvncserver CVS two new options (see the
- [345]wireframe FAQ and [346]scrollcopyrect FAQ below) provide schemes
+ [347]wireframe FAQ and [348]scrollcopyrect FAQ below) provide schemes
to sweep this problem under the rug for window moves or resizes and
for some (but not all) window scrolls.
@@ -3186,8 +3200,8 @@ 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 [347]slow video
- card read rates (see [348]here too). A displacement, even a small one,
+ of the intermediate steps. BTW the lurching is due to [349]slow video
+ card read rates (see [350]here too). 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.
@@ -3195,7 +3209,7 @@ ied)
for -wireframe to do any good.
The mode is currently on by default because most people are inflicted
- with the problem. It can be disabled with the [349]-nowireframe option
+ with the problem. It can be disabled with the [351]-nowireframe option
(aka -nowf). 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
@@ -3240,13 +3254,13 @@ ied)
* Maximum time to show a wireframe animation.
* Minimum time between sending wireframe outlines.
- See the [350]"-wireframe tweaks" option for more details. On a slow
+ See the [352]"-wireframe tweaks" option for more details. On a slow
link, e.g. dialup modem, the parameters may be automatically adjusted
for better response.
CopyRect encoding: In addition to the above there is the
- [351]"-wirecopyrect mode" option. It is also on by default. This
+ [353]"-wirecopyrect mode" option. It is also on by default. This
instructs x11vnc to not only 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 the
@@ -3294,7 +3308,7 @@ ied)
requiring the image data to be transmitted over the network. For fast
links the speedup is primarily due to x11vnc not having to read the
scrolled framebuffer data from the X server (recall that reading from
- the hardware framebuffer is [352]slow).
+ the hardware framebuffer is [354]slow).
To do this x11vnc uses the RECORD X extension to snoop the X11
protocol between the X client with the focus window and the X server.
@@ -3316,10 +3330,10 @@ ied)
the X server display: if one falls too far behind it could become a
mess...
- The initial implementation of [353]-scrollcopyrect option is useful in
+ The initial implementation of [355]-scrollcopyrect option is useful in
that it detects many scrolls and thus gives a much nicer working
- environment (especially when combined with the [354]-wireframe
- [355]-wirecopyrect [356]options, which are also on by default; and if
+ environment (especially when combined with the [356]-wireframe
+ [357]-wirecopyrect [358]options, which are also on by default; and if
you are willing to enable the ShadowFB things are very fast). The fact
that there aren't long delays or lurches during scrolling is the
primary improvement.
@@ -3352,10 +3366,10 @@ ied)
One can tap the Alt_L key (Left "Alt" key) 3 times in a row to
signal x11vnc to refresh the screen to all viewers. Your
VNC-viewer may have its own screen refresh hot-key or button. See
- also: [357]-fixscreen
+ also: [359]-fixscreen
* Some applications, notably OpenOffice, do XCopyArea scrolls in
weird ways that assume ancestor window clipping is taking place.
- See the [358]-scr_skip option for ways to tweak this on a
+ See the [360]-scr_skip option for ways to tweak this on a
per-application basis.
* Selecting text while dragging the mouse may be slower, especially
if the Button-down event happens near the window's edge. This is
@@ -3372,7 +3386,7 @@ ied)
because it fails to detect scrolls in it. Sometimes clicking
inside the application window or selecting some text in it to
force the focus helps.
- * When using the [359]-scale option there will be a quick CopyRect
+ * When using the [361]-scale option there will be a quick CopyRect
scroll, but it needs to be followed by a slower "cleanup" update.
This is because for a fixed finite screen resolution (e.g. 75 dpi)
scaling and copyrect-ing are not exactly independent. Scaling
@@ -3385,7 +3399,7 @@ ied)
If you find the -scrollcopyrect behavior too approximate or
distracting you can go back to the standard polling-only update method
- with the [360]-noscrollcopyrect (or -noscr for short). If you find
+ with the [362]-noscrollcopyrect (or -noscr for short). If you find
some extremely bad and repeatable behavior for -scrollcopyrect please
report a bug.
@@ -3424,16 +3438,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 "[361]-cursor X" option that
+ A simple kludge is provided by the "[363]-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 "[362]-cursor some" option for
+ work for those cases. Also see the "[364]-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 [363]-overlay option is supplied. See [364]this FAQ
+ cursor when the [365]-overlay option is supplied. See [366]this FAQ
for more info.
Also as of Dec/2004 in the libvncserver CVS XFIXES X extension support
@@ -3441,7 +3455,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 [365]Solaris 10.
+ distros and [367]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
@@ -3449,7 +3463,7 @@ ied)
situations where the 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. [366]Details can be found here.
+ hidden alpha channel data under 32bpp. [368]Details can be found here.
Q-58: When using XFIXES cursorshape mode, some of the cursors look
@@ -3482,17 +3496,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 "[367]-alphacut n" option lets
+ course!) some tunable parameters. The "[369]-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 "[368]-alphafrac f" option tries to correct individual
+ 240. The "[370]-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 [369]-alpharemove that is useful for
+ Finally, there is an option [371]-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
@@ -3518,11 +3532,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 [370]-nocursorshape x11vnc option.
+ disabled for all clients with the [372]-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
- [371]-noalphablend option to disable this behavior (always approximate
+ [373]-noalphablend option to disable this behavior (always approximate
transparent cursors with opaque RGB values).
The CursorShapeUpdates VNC extension complicates matters because the
@@ -3550,9 +3564,9 @@ ied)
Q-60: 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 [372]tightvnc extension
+ This default takes advantage of a [374]tightvnc extension
(CursorShapeUpdates) that allows specifying a cursor image shape for
- the local VNC viewer. You may disable it with the [373]-nocursor
+ the local VNC viewer. You may disable it with the [375]-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
@@ -3566,18 +3580,18 @@ ied)
clients (i.e. passive viewers can see the mouse cursor being moved
around by another viewer)?
- Use the [374]-cursorpos option when starting x11vnc. A VNC viewer must
+ Use the [376]-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 [375]-nocursorpos
- and [376]-nocursorshape.
+ libvncserver CVS -cursorpos is the default. See also [377]-nocursorpos
+ and [378]-nocursorshape.
Q-62: 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: [377]-buttonmap
+ You can remap the mouse buttons via something like: [379]-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.
@@ -3585,7 +3599,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 [378]-debug_pointer option prints out much info for
+ Note that the [380]-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
@@ -3607,7 +3621,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 [379]-buttonmap but rather configuring the X server
+ consider not using [381]-buttonmap but rather configuring the X server
to think it has a mouse with 5 buttons even though the physical mouse
does not. (e.g. 'Option "ZAxisMapping" "4 5"').
@@ -3637,7 +3651,7 @@ ied)
Q-63: How can I get my AltGr and Shift modifiers to work between
keyboards for different languages?
- The option [380]-modtweak should help here. It is a mode that monitors
+ The option [382]-modtweak should help here. 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.
@@ -3646,17 +3660,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 [381]this FAQ
+ and ">" it. This key does not exist on the keyboard (see [383]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 [382]FAQ about the -xkb option for a more powerful method
+ Also see the [384]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
- [383]-debug_keyboard option prints out much info for every keystroke
+ [385]-debug_keyboard option prints out much info for every keystroke
and so can be useful debugging things.
@@ -3668,9 +3682,9 @@ ied)
(e.g. pc105 in the XF86Config file when it should be something else,
say pc104).
- Short Cut: Try the [384]-xkb or [385]-sloppy_keys options and see if
+ Short Cut: Try the [386]-xkb or [387]-sloppy_keys options and see if
that helps the situation. The discussion below is a bit outdated (e.g.
- [386]-modtweak is now the default) but is useful reference for various
+ [388]-modtweak is now the default) but is useful reference for various
tricks and so is kept.
@@ -3713,17 +3727,17 @@ ied)
-remap less-comma
These are convenient in that they do not modify the actual X server
- settings. The former ([387]-modtweak) is a mode that monitors the
+ settings. The former ([389]-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 ([388]-remap less-comma) is an immediate remapping of the
+ The latter ([390]-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 [389]FAQ about the -xkb option as a possible workaround
+ See also the [391]FAQ about the -xkb option as a possible workaround
using the XKEYBOARD extension.
- Note that the [390]-debug_keyboard option prints out much info for
+ Note that the [392]-debug_keyboard option prints out much info for
every keystroke to aid debugging keyboard problems.
@@ -3731,13 +3745,13 @@ ied)
(i.e. an extra comma).
This is likely because you press "Shift" then "<" but then released
- the Shift key before releasing the "<". Because of a [391]keymapping
+ the Shift key before releasing the "<". Because of a [393]keymapping
ambiguity the last event "< up" is interpreted as "," because that key
unshifted is the comma.
- This should not happen in [392]-xkb mode, because it works hard to
+ This should not happen in [394]-xkb mode, because it works hard to
resolve the ambiguities. If you do not want to use -xkb, try the
- option [393]-sloppy_keys to attempt a similar type of algorithm.
+ option [395]-sloppy_keys to attempt a similar type of algorithm.
Q-66: I'm using an "international" keyboard (e.g. German "de", or
@@ -3761,7 +3775,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 [394]-modtweak
+ This all worked fine with x11vnc running with the [396]-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
@@ -3779,7 +3793,7 @@ ied)
* there is a new option -xkb to use the XKEYBOARD extension API to
do the Modifier key tweaking.
- The [395]-xkb option seems to fix all of the missing keys: "@", "<",
+ The [397]-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
@@ -3787,7 +3801,7 @@ ied)
debugging output (send it along with any problems you report).
Update: as of Jun/2005 x11vnc will try to automatically enable
- [396]-xkb if it appears that would be beneficial (e.g. if it sees any
+ [398]-xkb if it appears that would be beneficial (e.g. if it sees any
of "@", "<", ">", "[" and similar keys are mapped in a way that needs
the -xkb to access them). To disable this automatic check use -noxkb.
@@ -3802,7 +3816,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:
- [397]-skip_keycodes 93
+ [399]-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
@@ -3819,16 +3833,16 @@ 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 [398]-remap x11vnc option:
+ created using the [400]-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
- [399]-add_keysyms option in the next paragraph.
- Update: for convenience "[400]-remap DEAD" does many of these
+ [401]-add_keysyms option in the next paragraph.
+ Update: for convenience "[402]-remap DEAD" does many of these
mappings at once.
- * To complement the above workaround using the [401]-remap, an
- option [402]-add_keysyms was added. This option instructs x11vnc
+ * To complement the above workaround using the [403]-remap, an
+ option [404]-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
@@ -3847,7 +3861,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) [403]-norepeat x11vnc option. You will still
+ use the new (Jul/2004) [405]-norepeat x11vnc option. You will still
have autorepeating because that is taken care of on your VNC viewer
side.
@@ -3871,7 +3885,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 [404]-norepeat (which has since Dec/2004 been
+ needed, or to use the [406]-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
@@ -3882,7 +3896,7 @@ ied)
keystrokes!!
Are you using x11vnc to log in to an X session? (as described in
- [405]this FAQ) If so, x11vnc is starting before your session and it
+ [407]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
@@ -3906,7 +3920,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 "[406]-remap Super_R-Mode_switch" x11vnc option may
+ Something like "[408]-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)).
@@ -3929,7 +3943,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 [407]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
+ the [409]-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 in Unix.
@@ -3940,7 +3954,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 [408]-remap
+ have x11vnc do the remapping. This can be done via the [410]-remap
option using the fake "keysyms" Button1, Button2, etc. as the "to"
keys (i.e. the ones after the "-")
@@ -3949,7 +3963,7 @@ ied)
button "paste" because (using XFree86/Xorg Emulate3Buttons) you have
to click both buttons on the touch pad at the same time. This
remapping:
- [409]-remap Super_R-Button2
+ [411]-remap Super_R-Button2
maps the Super_R "flag" key press to the Button2 click, thereby making
X pasting a bit easier.
@@ -3979,7 +3993,7 @@ ied)
There may also be scaling viewers out there (e.g. TightVNC or UltraVNC
on Windows) that automatically shrink or expand the remote framebuffer
to fit the local display. Especially for hand-held devices. See also
- [410]this FAQ on x11vnc scaling.
+ [412]this FAQ on x11vnc scaling.
Q-73: Does x11vnc support server-side framebuffer scaling? (E.g. to
@@ -3987,7 +4001,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 "[411]-scale fraction"
+ per-client setting. To enable it use the "[413]-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.
@@ -4008,7 +4022,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
- [412]applications. Since with integer scale factors the framebuffers
+ [414]applications. Since with integer scale factors the framebuffers
become huge and scaling operations time consuming, be sure to use
":nb" for the fastest response.
@@ -4034,12 +4048,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 ([413]-rfbport option,
+ different scalings listening on separate ports ([415]-rfbport option,
etc.).
BTW, whenever you run two or more x11vnc's on the same X display and
- use the [414]GUI, then to avoid all of the x11vnc's simultaneously
- answering the gui you will need to use something like [415]"-connect
+ use the [416]GUI, then to avoid all of the x11vnc's simultaneously
+ answering the gui you will need to use something like [417]"-connect
file1 -gui ..." with different connect files for each x11vnc you want
to control via the gui (or remote-control). The "-connect file1" usage
gives separate communication channels between a x11vnc proces and the
@@ -4048,7 +4062,7 @@ ied)
Update: 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 [416]"-scale_cursor frac" option to set the cursor
+ want that, use the [418]"-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).
@@ -4070,16 +4084,16 @@ ied)
screen is not 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 [417]-blackout x11vnc option
+ may be distracting to the viewer. The [419]-blackout x11vnc option
allows you to blacken-out rectangles by manually specifying their
WxH+X+Y geometries. If your system has the libXinerama library, the
- [418]-xinerama x11vnc option can be used to have it automatically
+ [420]-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 [419]-xwarppointer
+ of the large display. If this happens try using the [421]-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
@@ -4104,23 +4118,23 @@ 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 [420]FAQ to increase the limit. It
- is probably also a good idea to run with the [421]-onetile option in
+ /etc/system as mentioned in another [422]FAQ to increase the limit. It
+ is probably also a good idea to run with the [423]-onetile option in
this case (to limit each x11vnc to 3 shm segments), or even
- [422]-noshm to use no shm segments.
+ [424]-noshm to use no shm segments.
Q-76: 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 "[423]-clip
+ As of Mar/2005 in the libvncserver CVS x11vnc has the "[425]-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. One user used -clip to split up a
- large [424]Xinerama screen into two more managable smaller screens.
+ large [426]Xinerama screen into two more managable smaller screens.
This also works to view a sub-region of a single application window if
- the [425]-id or [426]-sid options are used. The offset is measured
+ the [427]-id or [428]-sid options are used. The offset is measured
from the upper left corner of the selected window.
@@ -4129,7 +4143,7 @@ ied)
crash.
As of Dec/2004 in the libvncserver CVS x11vnc supports XRANDR. You
- enable it with the [427]-xrandr option to make x11vnc monitor XRANDR
+ enable it with the [429]-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.
@@ -4139,7 +4153,7 @@ ied)
then the 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 [428]-padgeom option to make the region big
+ viewers you can try the [430]-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
@@ -4193,9 +4207,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 [429]this FAQ
+ desktop in a separate Virtual Console (e.g. VC 8) (see [431]this FAQ
on VC's for background). Unfortunately, this Fullscreen VC is not an X
- server. So x11vnc cannot access it (however, [430]see this for a
+ server. So x11vnc cannot access it (however, [432]see this for a
possible partial workaround). x11vnc works fine with "Normal X
application window" and "Quick-Switch mode" because these use X.
@@ -4212,13 +4226,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 [431]is in the active VC.
+ as long as the VMWare X session [433]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 [432]-id windowid option. The
+ the VMWare menu buttons) by use of the [434]-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
@@ -4299,7 +4313,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 [433]X API, but you get
+ of Xvfb x11vnc can poll it much better via the [435]X API, but you get
the idea.
By default in -rawfb mode x11vnc will actually close any X display it
@@ -4352,7 +4366,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 [434]active VC) one
+ view and interact with VC #2 (assuming it is the [436]active VC) one
can run something like:
x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2'
@@ -4365,7 +4379,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
- [435]VMWare Fullscreen mode is actually viewable under -rawfb. But
+ [437]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...
@@ -4397,10 +4411,10 @@ 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 [436]-nosel option. If you
+ the Clipboard/Selection exchanged use the [438]-nosel option. If you
don't want the PRIMARY selection to be polled for changes use the
- [437]-noprimary option. You can also fine-tune it a bit with the
- [438]-seldir dir option.
+ [439]-noprimary option. You can also fine-tune it a bit with the
+ [440]-seldir dir option.
You may need to watch out for desktop utilities such as KDE's
"Klipper" that do odd things with the selection, clipboard, and
@@ -4412,7 +4426,7 @@ ied)
As of Oct/2005 x11vnc enables the TightVNC file transfer
implementation that was added to libvncserver. This currently only
works with TightVNC viewers (and Windows only it appears). It is on by
- default, to disable it use the [439]-nofilexfer option.
+ default, to disable it use the [441]-nofilexfer option.
Q-85: Why don't I hear the "Beeps" in my X session (e.g. when typing
@@ -4423,7 +4437,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 [440]-nobell option. If
+ If you don't want to hear the beeps use the [442]-nobell option. If
you want to hear the audio from the remote applications, consider
trying a redirector such as esd.
@@ -4439,7 +4453,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
- [441]email!
+ [443]email!
[PayPal]
@@ -4661,231 +4675,233 @@ References
214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 221. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
- 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 223. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
- 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
- 227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 228. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
- 229. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
- 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
- 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
- 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 241. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
- 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
- 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
- 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 223. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
+ 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
+ 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 230. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
+ 231. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
+ 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
+ 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 243. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
+ 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
- 251. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 252. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 253. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 256. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 257. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
- 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
+ 253. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 254. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 255. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 258. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 259. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
- 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 266. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 267. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 271. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh
- 272. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
- 276. ftp://ftp.x.org/
- 277. http://www.karlrunge.com/x11vnc/dtVncPopup
- 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 280. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 283. http://www.karlrunge.com/x11vnc/blockdpy.c
- 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
- 288. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 289. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 290. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
- 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 292. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
- 293. http://www.jirka.org/gdm-documentation/x241.html
- 294. http://www.karlrunge.com/x11vnc/x11vnc_loop
- 295. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
- 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
- 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 305. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 306. http://www.karlrunge.com/x11vnc/Xdummy
- 307. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 308. http://www.karlrunge.com/x11vnc/shm_clear
- 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 311. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
- 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 322. http://www.tightvnc.com/
- 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
- 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
- 335. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
- 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
- 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 339. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 268. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 269. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 273. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh
+ 274. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
+ 278. ftp://ftp.x.org/
+ 279. http://www.karlrunge.com/x11vnc/dtVncPopup
+ 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 282. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 285. http://www.karlrunge.com/x11vnc/blockdpy.c
+ 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
+ 290. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 291. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 292. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
+ 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 294. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
+ 295. http://www.jirka.org/gdm-documentation/x241.html
+ 296. http://www.karlrunge.com/x11vnc/x11vnc_loop
+ 297. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
+ 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
+ 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
+ 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 307. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 308. http://www.karlrunge.com/x11vnc/Xdummy
+ 309. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 310. http://www.karlrunge.com/x11vnc/shm_clear
+ 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 313. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
+ 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 324. http://www.tightvnc.com/
+ 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
+ 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
+ 337. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
+ 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
+ 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 341. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 345. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 346. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
- 347. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
- 348. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 347. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 348. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
+ 349. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 350. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 352. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 354. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
- 356. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
- 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 360. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 361. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 363. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 364. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
- 365. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
- 366. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 367. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
- 368. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
- 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
- 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 371. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
- 372. http://www.tightvnc.com/
- 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
- 375. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 376. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 377. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 378. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 354. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
+ 358. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 360. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
+ 361. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 363. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 364. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 366. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
+ 367. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
+ 368. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
+ 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
+ 371. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
+ 372. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
+ 374. http://www.tightvnc.com/
+ 375. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 376. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
+ 377. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 378. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
379. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 380. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 381. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 382. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 383. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 384. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 385. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 386. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 387. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 388. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 389. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 390. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 391. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 392. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
- 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 380. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 381. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 382. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 383. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 384. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 385. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 386. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 387. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 388. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 389. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 390. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 391. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 392. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 393. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 402. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 403. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 404. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 405. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 407. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 402. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 403. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 404. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 405. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 407. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
408. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
409. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 410. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 411. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 412. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
- 413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 414. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
- 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
- 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
- 420. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 421. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 423. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
- 424. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
- 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
- 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
- 429. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 430. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 411. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 412. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 414. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
+ 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
+ 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
+ 420. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 421. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
+ 422. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 423. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
+ 426. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
+ 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
+ 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
431. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 432. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 433. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 434. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 435. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
- 436. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
- 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
- 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer
- 440. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
- 441. mailto:xvml@karlrunge.com
+ 432. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 433. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 435. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 436. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 437. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
+ 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
+ 440. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
+ 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer
+ 442. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
+ 443. mailto:xvml@karlrunge.com
=======================================================================
diff --git a/x11vnc/help.c b/x11vnc/help.c
index 692276a..7cccbd4 100644
--- a/x11vnc/help.c
+++ b/x11vnc/help.c
@@ -173,7 +173,7 @@ void print_help(int mode) {
"\n"
" Note that even if there are *no* depth 24 visuals or\n"
" windows (i.e. pure 8bpp), this mode is potentially\n"
-" a improvement over -flashcmap because it avoids the\n"
+" an improvement over -flashcmap because it avoids the\n"
" flashing and shows each window in the correct color.\n"
"\n"
" This method appear to work, but may still have bugs\n"
@@ -183,12 +183,12 @@ void print_help(int mode) {
"\n"
" There may be painting errors for clipping and switching\n"
" between windows of depths 8 and 24. Heuristics are\n"
-" applied to try to minimize the painting errors.\n"
-" One can also press 3 Alt_L's in a row to refresh the\n"
-" screen if the error does not repair itself. Also the\n"
-" option -fixscreen 8=3.0 or -fixscreen V=3.0 may be\n"
-" use to periodically refresh the screen at the cost of\n"
-" bandwidth (every 3 sec for this example).\n"
+" applied to try to minimize the painting errors. One can\n"
+" also press 3 Alt_L's in a row to refresh the screen\n"
+" if the error does not repair itself. Also the option\n"
+" -fixscreen 8=3.0 or -fixscreen V=3.0 may be used to\n"
+" periodically refresh the screen at the cost of bandwidth\n"
+" (every 3 sec for this example).\n"
"\n"
" The [opts] string can contain the following settings.\n"
" Multiple settings are separated by commas.\n"
@@ -221,6 +221,11 @@ void print_help(int mode) {
" This may lead to the windows being unnoticed for this\n"
" amount of time when deiconifying, painting errors, etc.\n"
"\n"
+" While testing on a very old SS20 these options gave\n"
+" tolerable response: -8to24 poll=0.2,cachewin=5.0. For\n"
+" this machine -overlay is supported and gives better\n"
+" response.\n"
+"\n"
" Debugging for this mode can be enabled by setting \n"
" \"dbg=1\", \"dbg=2\", or \"dbg=3\".\n"
"\n"
diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1
index ca48b79..8eea209 100644
--- a/x11vnc/x11vnc.1
+++ b/x11vnc/x11vnc.1
@@ -205,7 +205,7 @@ framebuffer.
.IP
Note that even if there are *no* depth 24 visuals or
windows (i.e. pure 8bpp), this mode is potentially
-a improvement over \fB-flashcmap\fR because it avoids the
+an improvement over \fB-flashcmap\fR because it avoids the
flashing and shows each window in the correct color.
.IP
This method appear to work, but may still have bugs
@@ -215,12 +215,12 @@ iconify all but one for the colors to be correct.
.IP
There may be painting errors for clipping and switching
between windows of depths 8 and 24. Heuristics are
-applied to try to minimize the painting errors.
-One can also press 3 Alt_L's in a row to refresh the
-screen if the error does not repair itself. Also the
-option \fB-fixscreen\fR 8=3.0 or \fB-fixscreen\fR V=3.0 may be
-use to periodically refresh the screen at the cost of
-bandwidth (every 3 sec for this example).
+applied to try to minimize the painting errors. One can
+also press 3 Alt_L's in a row to refresh the screen
+if the error does not repair itself. Also the option
+\fB-fixscreen\fR 8=3.0 or \fB-fixscreen\fR V=3.0 may be used to
+periodically refresh the screen at the cost of bandwidth
+(every 3 sec for this example).
.IP
The [opts] string can contain the following settings.
Multiple settings are separated by commas.
@@ -253,6 +253,11 @@ XGetWindowAttributes results. E.g. cachewin=5.0.
This may lead to the windows being unnoticed for this
amount of time when deiconifying, painting errors, etc.
.IP
+While testing on a very old SS20 these options gave
+tolerable response: \fB-8to24\fR poll=0.2,cachewin=5.0. For
+this machine \fB-overlay\fR is supported and gives better
+response.
+.IP
Debugging for this mode can be enabled by setting
"dbg=1", "dbg=2", or "dbg=3".
.PP
diff --git a/x11vnc/x11vnc.h b/x11vnc/x11vnc.h
index fd46d09..3707c75 100644
--- a/x11vnc/x11vnc.h
+++ b/x11vnc/x11vnc.h
@@ -192,7 +192,9 @@ extern int xtrap_base_event_type;
#endif
#include <netdb.h>
+#ifndef _AIX
extern int h_errno;
+#endif
#if LIBVNCSERVER_HAVE_NETINET_IN_H
#include <netinet/in.h>