summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--prepare_x11vnc_dist.sh6
-rw-r--r--x11vnc/ChangeLog3
-rw-r--r--x11vnc/README1517
-rw-r--r--x11vnc/x11vnc.115
-rw-r--r--x11vnc/x11vnc.c116
5 files changed, 915 insertions, 742 deletions
diff --git a/prepare_x11vnc_dist.sh b/prepare_x11vnc_dist.sh
index 85c27b0..5efb75d 100644
--- a/prepare_x11vnc_dist.sh
+++ b/prepare_x11vnc_dist.sh
@@ -33,8 +33,8 @@ sed -e "s/Johannes.Schindelin@gmx.de/runge@karlrunge.com/gi" \
-e "s/Johannes.Schindelin/Karl Runge/g" \
-e "s/a library to make writing a vnc server easy/a VNC server for the current X11 session/" \
-e "/^%description$/,/%description devel$/d" \
- -e '/^Static libraries.*$/%description\
-x11vnc is to Xwindows what WinVNC is to Windows, i.e. a server\
+ -e 's/^Static libraries.*$/%description\
+x11vnc is to X Window System what WinVNC is to Windows, i.e. a server\
which serves the current Xwindows desktop via RFB (VNC) protocol\
to the user.\
\
@@ -45,7 +45,7 @@ x11vnc was put together and is (actively ;-) maintained by\
Karl Runge <runge@karlrunge.com>\
\
%prep\
-\1/' \
+/' \
> x11vnc.spec.in
mv libvncserver/Makefile.am libvncserver/Makefile.am.LibVNCServer
diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog
index 1e3180f..d28a311 100644
--- a/x11vnc/ChangeLog
+++ b/x11vnc/ChangeLog
@@ -1,3 +1,6 @@
+2005-11-28 Karl Runge <runge@karlrunge.com>
+ * x11vnc: add -loop option.
+
2005-11-25 Karl Runge <runge@karlrunge.com>
* x11vnc: throttle load if fb update requests not taking place.
* misc/x11vnc_pw: add utility script
diff --git a/x11vnc/README b/x11vnc/README
index ccef2d5..6be4643 100644
--- a/x11vnc/README
+++ b/x11vnc/README
@@ -1,5 +1,5 @@
-x11vnc README file Date: Sun Oct 23 00:01:08 EDT 2005
+x11vnc README file Date: Mon Nov 28 10:42:40 EST 2005
The following information is taken from these URLs:
@@ -920,197 +920,200 @@ make
[102]Q-24: How do I create a VNC password for use with x11vnc?
- [103]Q-25: Can I have two passwords for VNC viewers, one for full
+ [103]Q-25: Can I make it so -storepasswd doesn't show my password on
+ the screen?
+
+ [104]Q-26: Can I have two passwords for VNC viewers, one for full
access and the other for view-only access to the display?
- [104]Q-26: Can I fine tune what types of user input are allowed? E.g.
+ [105]Q-27: Can I fine tune what types of user input are allowed? E.g.
have some users just be able to move the mouse, but not click or type
anything?
- [105]Q-27: Why does x11vnc exit as soon as the VNC viewer disconnects?
+ [106]Q-28: Why does x11vnc exit as soon as the VNC viewer disconnects?
And why doesn't it allow more than one VNC viewer to connect at the
same time?
- [106]Q-28: Can I limit which machines incoming VNC clients can connect
+ [107]Q-29: Can I limit which machines incoming VNC clients can connect
from?
- [107]Q-29: How do I build x11vnc/libvncserver with libwrap
+ [108]Q-30: How do I build x11vnc/libvncserver with libwrap
(tcp_wrappers) support?
- [108]Q-30: Can I have x11vnc only listen on one network interface
+ [109]Q-31: Can I have x11vnc only listen on one network interface
(e.g. internal LAN) rather than having it listen on all network
interfaces and relying on -allow to filter unwanted connections out?
- [109]Q-31: Now that -localhost implies listening only on the loopback
+ [110]Q-32: Now that -localhost implies listening only on the loopback
interface, how I can occasionally allow in a non-localhost via the -R
allowonce remote control command?
- [110]Q-32: How can I tunnel my connection to x11vnc via an encrypted
+ [111]Q-33: How can I tunnel my connection to x11vnc via an encrypted
SSH channel between two Unix machines?
- [111]Q-33: How can I tunnel my connection to x11vnc via an encrypted
+ [112]Q-34: How can I tunnel my connection to x11vnc via an encrypted
SSH channel from Windows using an SSH client like Putty?
- [112]Q-34: Can I prompt the user at the local X display whether the
+ [113]Q-35: Can I prompt the user at the local X display whether the
incoming VNC client should be accepted or not? Can I decide to make
some clients view-only? How about running an arbitrary program to make
the decisions?
- [113]Q-35: Does x11vnc support Unix usernames and passwords? Can I
+ [114]Q-36: Does x11vnc support Unix usernames and passwords? Can I
further limit the set of Unix usernames who can connect to the VNC
desktop?
- [114]Q-36: I start x11vnc as root because it is launched via inetd(1)
+ [115]Q-37: I start x11vnc as root because it is launched via inetd(1)
or a display manager like gdm(1). Can I have x11vnc later switch to a
different user?
- [115]Q-37: I use a screen-lock when I leave my workstation (e.g.
+ [116]Q-38: I use a screen-lock when I leave my workstation (e.g.
xscreensaver or xlock). When I remotely access my workstation desktop
via x11vnc I can unlock the desktop fine, but I am worried people will
see my activities on the physical monitor. What can I do to prevent
this, or at least make it more difficult?
- [116]Q-38: Can I have x11vnc automatically lock the screen when I
+ [117]Q-39: Can I have x11vnc automatically lock the screen when I
disconnect the VNC viewer?
[Display Managers and Services]
- [117]Q-39: How can I run x11vnc as a "service" that is always
+ [118]Q-40: How can I run x11vnc as a "service" that is always
available?
- [118]Q-40: How can I use x11vnc to connect to an X login screen like
+ [119]Q-41: How can I use x11vnc to connect to an X login screen like
xdm, GNOME gdm, KDE kdm, or CDE dtlogin? (i.e. nobody is logged into
an X session yet).
- [119]Q-41: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
+ [120]Q-42: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
- [120]Q-42: How do I make x11vnc work with the Java VNC viewer applet
+ [121]Q-43: How do I make x11vnc work with the Java VNC viewer applet
in a web browser?
- [121]Q-43: Are reverse connections (i.e. the VNC server connecting to
+ [122]Q-44: Are reverse connections (i.e. the VNC server connecting to
the VNC viewer) using "vncviewer -listen" and vncconnect(1) supported?
- [122]Q-44: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a
+ [123]Q-45: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a
real display, but for a virtual one I keep around).
- [123]Q-45: How can I use x11vnc on "headless" machines? Why might I
+ [124]Q-46: How can I use x11vnc on "headless" machines? Why might I
want to?
[Resource Usage and Performance]
- [124]Q-46: I have lots of memory, but why does x11vnc fail with
+ [125]Q-47: I have lots of memory, but why does x11vnc fail with
shmget: No space left on device or Minor opcode of failed
request: 1 (X_ShmAttach)?
- [125]Q-47: How can I make x11vnc use less system resources?
+ [126]Q-48: How can I make x11vnc use less system resources?
- [126]Q-48: How can I make x11vnc use MORE system resources?
+ [127]Q-49: How can I make x11vnc use MORE system resources?
- [127]Q-49: I use x11vnc over a slow link with high latency (e.g.
+ [128]Q-50: I use x11vnc over a slow link with high latency (e.g.
dialup modem), is there anything I can do to speed things up?
- [128]Q-50: Does x11vnc support the X DAMAGE Xserver extension to find
+ [129]Q-51: Does x11vnc support the X DAMAGE Xserver extension to find
modified regions of the screen quickly and efficiently?
- [129]Q-51: When I drag windows around with the mouse or scroll up and
+ [130]Q-52: 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?
- [130]Q-52: Why not do something like wireframe animations to avoid the
+ [131]Q-53: Why not do something like wireframe animations to avoid the
windows "lurching" when being moved or resized?
- [131]Q-53: Can x11vnc try to apply heuristics to detect when an window
+ [132]Q-54: Can x11vnc try to apply heuristics to detect when an window
is scrolling its contents and use the CopyRect encoding for a speedup?
[Mouse Cursor Shapes]
- [132]Q-54: Why isn't the mouse cursor shape (the little icon shape
+ [133]Q-55: Why isn't the mouse cursor shape (the little icon shape
where the mouse pointer is) correct as I move from window to window?
- [133]Q-55: When using XFIXES cursorshape mode, some of the cursors
+ [134]Q-56: When using XFIXES cursorshape mode, some of the cursors
look really bad with extra black borders around the cursor and other
cruft. How can I improve their appearance?
- [134]Q-56: In XFIXES mode, are there any hacks to handle cursor
+ [135]Q-57: In XFIXES mode, are there any hacks to handle cursor
transparency ("alpha channel") exactly?
[Mouse Pointer]
- [135]Q-57: Why does the mouse arrow just stay in one corner in my
+ [136]Q-58: Why does the mouse arrow just stay in one corner in my
vncviewer, whereas my cursor (that does move) is just a dot?
- [136]Q-58: Can I take advantage of the TightVNC extension to the VNC
+ [137]Q-59: Can I take advantage of the TightVNC extension to the VNC
protocol where Cursor Positions Updates are sent back to all connected
clients (i.e. passive viewers can see the mouse cursor being moved
around by another viewer)?
- [137]Q-59: Is it possible to swap the mouse buttons (e.g. left-handed
+ [138]Q-60: 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?
[Keyboard Issues]
- [138]Q-60: How can I get my AltGr and Shift modifiers to work between
+ [139]Q-61: How can I get my AltGr and Shift modifiers to work between
keyboards for different languages?
- [139]Q-61: When I try to type a "<" (i.e. less than) instead I get ">"
+ [140]Q-62: When I try to type a "<" (i.e. less than) instead I get ">"
(i.e. greater than)! Strangely, typing ">" works OK!!
- [140]Q-62: When I try to type a "<" (i.e. less than) instead I get
+ [141]Q-63: When I try to type a "<" (i.e. less than) instead I get
"<," (i.e. an extra comma).
- [141]Q-63: I'm using an "international" keyboard (e.g. German "de", or
+ [142]Q-64: I'm using an "international" keyboard (e.g. German "de", or
Danish "dk") and the -modtweak mode works well if the VNC viewer is
run on a Unix/Linux machine with a similar keyboard. But if I run
the VNC viewer on Unix/Linux with a different keyboard (e.g. "us") or
Windows with any keyboard, I can't type some keys like: "@", "$",
"<", ">", etc. How can I fix this?
- [142]Q-64: When typing I sometimes get double, triple, or more of my
+ [143]Q-65: When typing I sometimes get double, triple, or more of my
keystrokes repeated. I'm sure I only typed them once, what can I do?
- [143]Q-65: The x11vnc -norepeat mode is in effect, but I still get
+ [144]Q-66: The x11vnc -norepeat mode is in effect, but I still get
repeated keystrokes!!
- [144]Q-66: The machine where I run x11vnc has an AltGr key, but the
+ [145]Q-67: The machine where I run x11vnc has an AltGr key, but the
local 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?
- [145]Q-67: I have a Sun machine I run x11vnc on. Its Sun keyboard has
+ [146]Q-68: I have a Sun machine I run x11vnc on. Its Sun keyboard has
just one Alt key labelled "Alt" and two Meta keys labelled with little
diamonds. The machine where I run the VNC viewer only has Alt keys.
How can I send a Meta keypress? (e.g. emacs needs this)
- [146]Q-68: Can I map a keystroke to a mouse button click on the remote
+ [147]Q-69: Can I map a keystroke to a mouse button click on the remote
machine?
[Screen Related Issues and Features]
- [147]Q-69: The remote display is larger (in number of pixels) than the
+ [148]Q-70: The remote display is larger (in number of pixels) than the
local display I am running the vncviewer on. I don't like the
vncviewer scrollbars, what I can do?
- [148]Q-70: Does x11vnc support server-side framebuffer scaling? (E.g.
+ [149]Q-71: Does x11vnc support server-side framebuffer scaling? (E.g.
to make the desktop smaller).
- [149]Q-71: Does x11vnc work with Xinerama? (i.e. multiple monitors
+ [150]Q-72: Does x11vnc work with Xinerama? (i.e. multiple monitors
joined together to form one big, single screen).
- [150]Q-72: Can I use x11vnc on a multi-headed display that is not
+ [151]Q-73: Can I use x11vnc on a multi-headed display that is not
Xinerama (i.e. separate screens :0.0, :0.1, ... for each monitor)?
- [151]Q-73: Can x11vnc show only a portion of the display? (E.g. for a
+ [152]Q-74: Can x11vnc show only a portion of the display? (E.g. for a
special purpose rfb application).
- [152]Q-74: Does x11vnc support the XRANDR (X Resize, Rotate and
+ [153]Q-75: Does x11vnc support the XRANDR (X Resize, Rotate and
Reflection) extension? Whenever I rotate or resize the screen x11vnc
just seems to crash.
- [153]Q-75: Why is the view in my VNC viewer completely black? Or why
+ [154]Q-76: Why is the view in my VNC viewer completely black? Or why
is everything flashing around randomly?
- [154]Q-76: I use Linux Virtual Consoles (VC's) to implement 'Fast User
+ [155]Q-77: I use Linux Virtual Consoles (VC's) to implement 'Fast User
Switching' between users' sessions (e.g. Betty is on Ctrl-Alt-F7,
Bobby is on Ctrl-Alt-F8, and Sid is on Ctrl-Alt-F1: they use those
keystrokes to switch between their sessions). How come the view in a
@@ -1118,12 +1121,12 @@ make
otherwise all messed up unless the X session x11vnc is attached to is
in the active VC?
- [155]Q-77: Can I use x11vnc to view my VMWare session remotely?
+ [156]Q-78: Can I use x11vnc to view my VMWare session remotely?
- [156]Q-78: Can non-X devices (e.g. a raw framebuffer) be viewed and/or
+ [157]Q-79: Can non-X devices (e.g. a raw framebuffer) be viewed and/or
controlled by x11vnc?
- [157]Q-79: I am using x11vnc where my local machine has "popup/hidden
+ [158]Q-80: I am using x11vnc where my local machine has "popup/hidden
taskbars" (e.g. GNOME or MacOS X) and the remote display where x11vnc
runs also has "popup/hidden taskbars" (e.g. GNOME). When I move the
mouse to the edge of the screen where the popups happen, the taskbars
@@ -1131,13 +1134,13 @@ make
[Misc: Clipboard, Beeps, Thanks, etc.]
- [158]Q-80: Does the Clipboard/Selection get transferred between the
+ [159]Q-81: Does the Clipboard/Selection get transferred between the
vncviewer and the X display?
- [159]Q-81: Why don't I hear the "Beeps" in my X session (e.g. when
+ [160]Q-82: Why don't I hear the "Beeps" in my X session (e.g. when
typing tput bel in an xterm)?
- [160]Q-82: Thanks for your program and for your help! Can I make a
+ [161]Q-83: Thanks for your program and for your help! Can I make a
donation?
_________________________________________________________________
@@ -1150,7 +1153,7 @@ make
For the former error, you need to specify the X display to connect to
(it also needs to be on the same machine the x11vnc process is to run
- on). Set your DISPLAY environment variable or use the [161]-display
+ on). Set your DISPLAY environment variable or use the [162]-display
option to specify it. Nearly always the correct value will be ":0"
@@ -1167,7 +1170,7 @@ make
How to Solve: See the xauth(1), Xsecurity(7), and xhost(1) man pages
for much info on X11 permissions. For example, you may need to set
- your XAUTHORITY environment variable or use the [162]-auth option to
+ your XAUTHORITY environment variable or use the [163]-auth option to
point to the correct MIT-MAGIC-COOKIE file (e.g. /home/joe/.Xauthority
or /var/gdm/:0.Xauth or /var/lib/kdm/A:0-crWk72K), or simply be sure
you run x11vnc as the correct user (i.e. the user who is logged into
@@ -1185,7 +1188,7 @@ make
x11vnc -display :0 -auth /var/gdm/:0.Xauth
(this is for the display manager gdm and requires root permission to
- read the gdm cookie file, see [163]this faq for other display manager
+ read the gdm cookie file, see [164]this faq for other display manager
cookie file names).
Less safe, but to avoid figuring out where the correct XAUTHORITY file
@@ -1194,7 +1197,7 @@ make
(from the same machine). The person could then type "xhost -localhost"
after x11vnc has connected to go back to the default permissions.
Also, for some situations the "-users lurk=" option may be of use
- (please read the documentation on the [164]-users option).
+ (please read the documentation on the [165]-users option).
To test out your X11 permissions from a remote shell, set DISPLAY and
possibly XAUTHORITY (see your shell's man page, bash(1), tcsh(1), on
@@ -1306,7 +1309,7 @@ h
earlier and perhaps non-Solaris):
First use the environment settings (CPPFLAGS, LDFLAGS, etc.) in the
- above [165]Solaris build script to run the configure command. That
+ above [166]Solaris build script to run the configure command. That
should succeed without failure. Then you have to hand edit the
autogenerated rfb/rfbconfig.h file in the source tree, and just before
the last #endif at the bottom of that file insert these workaround
@@ -1332,7 +1335,7 @@ typedef unsigned int in_addr_t;
on other older OS (Solaris, Linux, ...) releases.
Here are some notes for similar steps that need to be done to build on
- [166]SunOS 4.x
+ [167]SunOS 4.x
Please let us know if you had to use the above workaround (and whether
it worked or not). If there is enough demand we will try to push clean
@@ -1342,23 +1345,23 @@ typedef unsigned int in_addr_t;
Q-5: Where can I get a precompiled x11vnc binary for my Operating
System?
- Hopefully the [167]build steps above and [168]FAQ provide enough info
+ Hopefully the [168]build steps above and [169]FAQ provide enough info
for a painless compile for most environments. Please report problems
with the x11vnc configure, make, etc. on your system (if your system
is known to compile other GNU packages successfully).
There are precompiled x11vnc binaries built by other groups that are
available at the following locations:
- Debian: (.deb) [169]http://packages.debian.org/x11vnc
+ Debian: (.deb) [170]http://packages.debian.org/x11vnc
- Slackware: (.tgz) [170]http://www.linuxpackages.net/ Redhat/Fedora:
- (.rpm) [171]http://dag.wieers.com/packages/x11vnc/ SuSE: (.rpm)
- [172]http://linux01.gwdg.de/~pbleser/ Solaris: (pkg)
- [173]http://www.sunfreeware.com/ wwexptools: (.tgz)
- [174]http://www.bell-labs.com/project/wwexptools/packages.html
+ Slackware: (.tgz) [171]http://www.linuxpackages.net/ Redhat/Fedora:
+ (.rpm) [172]http://dag.wieers.com/packages/x11vnc/ SuSE: (.rpm)
+ [173]http://linux01.gwdg.de/~pbleser/ Solaris: (pkg)
+ [174]http://www.sunfreeware.com/ wwexptools: (.tgz)
+ [175]http://www.bell-labs.com/project/wwexptools/packages.html
If the above binaries don't work and building x11vnc on your OS fails
- (and all else fails!) you can try one of [175]my collection of
+ (and all else fails!) you can try one of [176]my collection of
binaries for various OS's and x11vnc releases.
As a general note, the x11vnc program is simple enough you don't
@@ -1379,9 +1382,9 @@ typedef unsigned int in_addr_t;
To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix)
try here:
- * [176]http://www.tightvnc.com/download.html
- * [177]http://www.realvnc.com/download-free.html
- * [178]http://sourceforge.net/projects/cotvnc/
+ * [177]http://www.tightvnc.com/download.html
+ * [178]http://www.realvnc.com/download-free.html
+ * [179]http://sourceforge.net/projects/cotvnc/
Q-7: How can I see all of x11vnc's command line options and
@@ -1389,7 +1392,7 @@ typedef unsigned int in_addr_t;
Run: x11vnc -opts to list just the option names or run: x11vnc
-help for long descriptions about each option. The output is listed
- [179]here as well.
+ [180]here as well.
Q-8: I don't like typing arcane command line options every time I
@@ -1420,10 +1423,10 @@ display :0
The /usr/bin/wish program is needed for operation. The gui is not
particularly user-friendly, it just provides a point and click mode to
set all the many x11vnc parameters and obtain help on them. See the
- [180]-gui option for more info. Examples: "x11vnc ... -gui" and
+ [181]-gui option for more info. Examples: "x11vnc ... -gui" and
"x11vnc ... -gui other:0" in the latter case the gui is displayed on
other:0, not the X display x11vnc is polling. There is also a
- "[181]-gui tray" system tray mode.
+ "[182]-gui tray" system tray mode.
Q-9: How can I get the GUI to run in the System Tray, or at least be a
@@ -1450,11 +1453,11 @@ display :0
Q-10: Can I make x11vnc more quiet and also go into the background
after starting up?
- Use the [182]-q and [183]-bg options, respectively. (also: -quiet is
+ Use the [183]-q and [184]-bg options, respectively. (also: -quiet is
an alias for -q)
Note that under -bg the stderr messages will be lost unless you use
- the "[184]-o logfile" option.
+ the "[185]-o logfile" option.
Q-11: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with
@@ -1475,7 +1478,7 @@ display :0
As of Mar/2004 in the libvncserver cvs there are a few such options.
They are enabled by adding something like -Dxxxx=1 to the CPPFLAGS
- environment variable before running configure (see the [185]build
+ environment variable before running configure (see the [186]build
notes for general background).
* -DVNCSHARED=1 make -shared the default.
* -DFOREVER=1 make -forever the default.
@@ -1524,21 +1527,21 @@ display :0
dual-screen mode to pass the keystrokes and mouse motions to the X11
display?
- Yes, for best response start up x11vnc with the "[186]-nofb" option
+ Yes, for best response start up x11vnc with the "[187]-nofb" option
(disables framebuffer polling, and does other optimizations) on the
secondary display (X11) machine. Then start up Win2VNC on the primary
display (Windows) referring it to the secondary display.
- This will also work X11 to X11 using [187]x2vnc, however you would
+ This will also work X11 to X11 using [188]x2vnc, however you would
probably just want to avoid VNC and use x2x for that.
For reference, here are some links to Win2VNC-like programs for
multiple monitor setups:
- * [188]Original Win2VNC
- * [189]Enhanced Win2VNC and [190]sourceforge link
- * [191]x2vnc
- * [192]x2x also [193]here
- * [194]zvnc (MorphOS)
+ * [189]Original Win2VNC
+ * [190]Enhanced Win2VNC and [191]sourceforge link
+ * [192]x2vnc
+ * [193]x2x also [194]here
+ * [195]zvnc (MorphOS)
All of them will work with x11vnc (except x2x where it is not needed).
@@ -1558,7 +1561,7 @@ display :0
on your display to be depth 24 TrueColor? Sun machines often have 8+24
overlay/multi-depth visuals, and you can make the default visual depth
24 TrueColor (see fbconfig(1) and Xsun(1)). 2) As of Feb/2004, in the
- libvncserver CVS, x11vnc has the [195]-visual option to allow you to
+ libvncserver CVS, x11vnc has the [196]-visual option to allow you to
force the framebuffer visual to whatever you want (this usually messes
up the colors unless you are very clever). In this case, the option
provides a convenient workaround for the Win2VNC bug:
@@ -1573,7 +1576,7 @@ display :0
PseudoColor (i.e. only 256 distinct colors). The x11vnc colors may
start out OK, but after a while they are incorrect in certain windows.
- Use the [196]-flashcmap option to have x11vnc watch for changes in the
+ Use the [197]-flashcmap option to have x11vnc watch for changes in the
colormap, and propagate those changes back to connected clients. This
can be slow (since the whole screen must be updated over the network
whenever the colormap changes). This flashing colormap behavior often
@@ -1582,7 +1585,7 @@ display :0
example of this. Consider reconfiguring the system to 16 bpp or depth
24 TrueColor if at all possible.
- Also note that in some rare cases the [197]-notruecolor option has
+ Also note that in some rare cases the [198]-notruecolor option has
corrected colors on 8bpp displays. The red, green, and blue masks were
non-zero in 8bpp PseudoColor on an obscure setup, and this option
corrected the problems.
@@ -1593,10 +1596,10 @@ display :0
different color depths: e.g. there are both depth 8 and 24 visuals
available at the same time.
- You may want to review the [198]previous question regarding 8 bpp
+ You may want to review the [199]previous question regarding 8 bpp
PseudoColor.
- On some hardware (Sun/SPARC, Sgi), the [199]-overlay option discussed
+ On some hardware (Sun/SPARC, Sgi), the [200]-overlay option discussed
a couple paragraphs down may solve this for you (you may want to skip
to it directly).
@@ -1634,7 +1637,7 @@ TrueColor defdepth 24
The -overlay mode: Another option is if the system with overlay
visuals is a Sun system running Solaris or Sgi running IRIX you can
- use the [200]-overlay x11vnc option (Aug/2004) to have x11vnc use the
+ use the [201]-overlay x11vnc option (Aug/2004) to have x11vnc use the
Solaris XReadScreen(3X11) function to poll the "true view" of the
whole screen at depth 24 TrueColor. XReadDisplay(3X11) is used on
IRIX. This is useful for Legacy applications (older versions of
@@ -1656,7 +1659,7 @@ TrueColor defdepth 24
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 [201]-id option to
+ possible workaround in this case is to use the [202]-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).
@@ -1664,7 +1667,7 @@ TrueColor defdepth 24
It is theoretically possible to solve this problem in general (see
xwd(1) for example), but it does not seem trivial or sufficiently fast
for x11vnc to be able to do so in real time. Fortunately the
- [202]-overlay option works for Solaris machines with overlay visuals
+ [203]-overlay option works for Solaris machines with overlay visuals
where most of this problem occurs.
@@ -1675,9 +1678,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 [203]color problems.
+ debugging x11vnc [204]color problems.
- Also, as of Dec/2004 libvncserver CVS you can use "[204]-id pick" to
+ Also, as of Dec/2004 libvncserver CVS you can use "[205]-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.
@@ -1695,7 +1698,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 [205]-sid windowid option ("shifted" windowid).
+ polling, try the [206]-sid windowid option ("shifted" windowid).
Q-19: My X display is depth 24 at 24bpp (instead of the normal depth
@@ -1745,15 +1748,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 [206]-display option to point the display to that of
+ machine. Use the [207]-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 [207]-noshm option (this enables the polling over
+ and also supply the [208]-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 [208]-flipbyteorder if the
+ on the polling rate. You may also need [209]-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
@@ -1777,7 +1780,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
- [209]-auth option to point to the correct file). Other options include
+ [210]-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 -
@@ -1789,7 +1792,7 @@ TrueColor defdepth 24
details.
If the display name in the cookie file needs to be changed between the
- two hosts, see [210]this note on the "xauth add ..." command.
+ two hosts, see [211]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
@@ -1803,7 +1806,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 [211]poll
+ Not recommended, but as a last resort, you could have x11vnc [212]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...)
@@ -1834,17 +1837,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
- [212]-remote and [213]-query options. To shut down the running x11vnc
+ [213]-remote and [214]-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 [214]-forever option has not been supplied, x11vnc will
+ If the [215]-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 [215]-bg option
+ If you have not put x11vnc in the background via the [216]-bg option
or shell & operator, then simply press Ctrl-C in the shell where
x11vnc is running to stop it.
@@ -1854,15 +1857,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 [216]-clear_mods
- option and [217]-clear_keys option can be used to release pressed keys
+ by tapping Ctrl, Shift, and Alt. Alternatively, the [217]-clear_mods
+ option and [218]-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 [218]-remote (same as -R) and [219]-query (same as -Q)
+ Look at the [219]-remote (same as -R) and [220]-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
@@ -1874,7 +1877,7 @@ TrueColor defdepth 24
be possible.
There is also a simple Tcl/Tk gui based on this remote control
- mechanism. See the [220]-gui option for more info. You will need to
+ mechanism. See the [221]-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".
@@ -1889,12 +1892,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" [221]option, which is the the same
+ the -storepasswd "pass" "file" [222]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: [222]-rfbauth
+ You then use the password via the x11vnc option: [223]-rfbauth
$HOME/myvncpasswd
Compared to vncpasswd(1) the latter two methods are a somewhat unsafe
@@ -1903,22 +1906,59 @@ 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 [223]-passwdfile and -passwd/-viewpasswd plain
+ x11vnc also has the [224]-passwdfile and -passwd/-viewpasswd plain
text (i.e. not obscured like the -rfbauth VNC passwords) password
options.
- Q-25: Can I have two passwords for VNC viewers, one for full access
+ Q-25: Can I make it so -storepasswd doesn't show my password on the
+ screen?
+
+ You can use the vncpasswd program from RealVNC or TightVNC mentioned
+ above..
+
+ Alternatively, this script should keep your [225]-storepasswd more
+ private:
+#!/bin/sh
+# usage: x11vnc_pw [file] (default: ~/.vnc/passwd)
+
+if [ "X$1" = "X" ]; then
+ file=$HOME/.vnc/passwd
+else
+ file=$1
+fi
+
+stty -echo
+printf "Password: "
+read pw1; echo ""
+printf "Verify: "
+read pw2; echo ""
+stty echo
+
+if [ "X$pw1" != "X$pw2" ]; then
+ echo "passwords do not match."
+ exit 1
+fi
+
+x11vnc -help > /dev/null 2>&1
+x11vnc -storepasswd "$pw1" "$file"
+ls -l "$file"
+
+ Note that there is a tiny window of time when x11vnc -storepasswd is
+ running that someone could snoop the value using ps(1).
+
+
+ Q-26: Can I have two passwords for VNC viewers, one for full access
and the other for view-only access to the display?
Yes, as of May/2004 in the libvncserver CVS there is the
- [224]-viewpasswd option to supply the view-only password. Note the
- full-access password option [225]-passwd must be supplied at the same
+ [226]-viewpasswd option to supply the view-only password. Note the
+ full-access password option [227]-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
- [226]-passwdfile option to specify a file containing plain text
+ [228]-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
@@ -1926,7 +1966,7 @@ TrueColor defdepth 24
it is taken as the view-only password. (use "__EMPTY__" to supply an
empty one).
- View-only passwords currently do not work for the [227]-rfbauth
+ View-only passwords currently do not work for the [229]-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
@@ -1936,11 +1976,11 @@ TrueColor defdepth 24
straight-forward to work out what to do from the VNC source code.
- Q-26: Can I fine tune what types of user input are allowed? E.g. have
+ Q-27: Can I fine tune what types of user input are allowed? E.g. have
some users just be able to move the mouse, but not click or type
anything?
- As of Feb/2005, the [228]-input option allows you to do this. "K",
+ As of Feb/2005, the [230]-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
@@ -1950,29 +1990,29 @@ TrueColor defdepth 24
remote control mechanism or the GUI. E.g. x11vnc -R input:hostname:M
- Q-27: Why does x11vnc exit as soon as the VNC viewer disconnects? And
+ Q-28: Why does x11vnc exit as soon as the VNC viewer disconnects? And
why doesn't it allow more than one VNC viewer to connect at the same
time?
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 [229]-forever option (aka -many) to have
+ periods of time. Use the [231]-forever option (aka -many) to have
x11vnc wait for more connections after the first client disconnects.
- Use the [230]-shared option to have x11vnc allow multiple clients to
+ Use the [232]-shared option to have x11vnc allow multiple clients to
connect simultaneously.
- Recommended additional safety measures include using ssh ([231]see
+ Recommended additional safety measures include using ssh ([233]see
above), stunnel, or a VPN to authenticate and encrypt the viewer
- connections or to at least use the -rfbauth passwd-file [232]option to
- use VNC password protection (or [233]-passwdfile) It is up to YOU to
+ connections or to at least use the -rfbauth passwd-file [234]option to
+ use VNC password protection (or [235]-passwdfile) It is up to YOU to
apply these security measures, they will not be done for you
automatically.
- Q-28: Can I limit which machines incoming VNC clients can connect
+ Q-29: Can I limit which machines incoming VNC clients can connect
from?
- Yes, look at the [234]-allow and [235]-localhost options to limit
+ Yes, look at the [236]-allow and [237]-localhost options to limit
connections by hostname or IP address. E.g.
x11vnc -allow 192.168.0.1,192.168.0.2
@@ -1984,11 +2024,11 @@ TrueColor defdepth 24
Note that -localhost is the same as "-allow 127.0.0.1"
For more control, build libvncserver with libwrap support
- [236](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
+ [238](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
for complete details.
- Q-29: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers)
+ Q-30: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers)
support?
Here is one way to pass this information to the configure script:
@@ -2004,50 +2044,50 @@ TrueColor defdepth 24
is "vnc", e.g.:
vnc: 192.168.100.3 .example.com
- Note that if you run x11vnc out of [237]inetd you do not need to build
+ Note that if you run x11vnc out of [239]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.
- Q-30: Can I have x11vnc only listen on one network interface (e.g.
+ Q-31: Can I have x11vnc only listen on one network interface (e.g.
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 "[238]-listen
+ As of Mar/2005 in the libvncserver CVS, there is the "[240]-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 "[239]-allow host1,..." option to allow only specific hosts
+ use the "[241]-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 [240]-localhost now implies "-listen localhost" since that
+ The option [242]-localhost now implies "-listen localhost" since that
is what most people expect it to do.
- Q-31: Now that -localhost implies listening only on the loopback
+ Q-32: Now that -localhost implies listening only on the loopback
interface, how I can occasionally allow in a non-localhost via the -R
allowonce remote control command?
- To do this specify "[241]-allow localhost". Unlike [242]-localhost
+ To do this specify "[243]-allow localhost". Unlike [244]-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
- ([243]-listen option) via remote control or gui, you may need to also
- manually adjust the [244]-allow list if you unexpectedly get into a
+ ([245]-listen option) via remote control or gui, you may need to also
+ manually adjust the [246]-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 [245]-localhost on
+ in on the listening interface. If you just toggle [247]-localhost on
and off x11vnc should see to it that you never get into such a state.
- Q-32: How can I tunnel my connection to x11vnc via an encrypted SSH
+ Q-33: 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 [246]how to tunnel VNC via
+ See the description earlier on this page on [248]how to tunnel VNC via
SSH from Unix to Unix. A number of ways are described along with some
issues you may encounter.
@@ -2055,10 +2095,10 @@ TrueColor defdepth 24
VPNs, etc.
- Q-33: How can I tunnel my connection to x11vnc via an encrypted SSH
+ Q-34: How can I tunnel my connection to x11vnc via an encrypted SSH
channel from Windows using an SSH client like Putty?
- [247]Above we described how to tunnel VNC via SSH from Unix to Unix,
+ [249]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
@@ -2081,8 +2121,8 @@ TrueColor defdepth 24
process in a BAT file including launching the VNC viewer by using the
plink Putty utility. Send us the script if you get that working.
- For extra protection feel free to run x11vnc with the [248]-localhost
- and [249]-rfbauth/[250]-passwdfile options.
+ For extra protection feel free to run x11vnc with the [250]-localhost
+ and [251]-rfbauth/[252]-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
@@ -2090,22 +2130,22 @@ TrueColor defdepth 24
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 [251]chaining ssh's.
+ automated by [253]chaining ssh's.
- As discussed [252]above another option is to first start the VNC
+ As discussed [254]above another option is to first start the VNC
viewer in "listen" mode, and then launch x11vnc with the
- "[253]-connect localhost" option to establish the reverse connection.
+ "[255]-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).
- Q-34: Can I prompt the user at the local X display whether the
+ Q-35: Can I prompt the user at the local X display whether the
incoming VNC client should be accepted or not? Can I decide to make
some clients view-only? How about running an arbitrary program to make
the decisions?
- Yes, look at the "[254]-accept command" option, it allows you to
+ Yes, look at the "[256]-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
@@ -2124,7 +2164,7 @@ TrueColor defdepth 24
own simple popup window. To accept the client press "y" or click mouse
on the "Yes" button. To reject the client press "n" or click mouse on
the "No" button. To accept the client View-only, press "v" or click
- mouse on the "View" button. If the [255]-viewonly option has been
+ mouse on the "View" button. If the [257]-viewonly option has been
supplied, the "View" action will not be present: the whole display is
view only in that case.
@@ -2140,7 +2180,7 @@ TrueColor defdepth 24
program to prompt the user whether the client should be accepted or
not. This requires that you have xmessage installed and available via
PATH. In case it is not already on your system, the xmessage program
- is available at [256]ftp://ftp.x.org/
+ is available at [258]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
@@ -2179,7 +2219,7 @@ elif [ $rc = 4 ]; then
fi
exit 1
- Stefan Radman has written a nice dtksh script [257]dtVncPopup for use
+ Stefan Radman has written a nice dtksh script [259]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.
@@ -2188,14 +2228,14 @@ 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 "[258]-gone
+ To run a command when a client disconnects, use the "[260]-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
be "gone").
- Q-35: Does x11vnc support Unix usernames and passwords? Can I further
+ Q-36: Does x11vnc support Unix usernames and passwords? Can I further
limit the set of Unix usernames who can connect to the VNC desktop?
Until the VNC protocol and libvncserver support this things will be
@@ -2203,13 +2243,13 @@ exit 1
such support.
One approximate method involves starting x11vnc with the
- [259]-localhost option. This basically requires the viewer user to log
+ [261]-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 [260]elsewhere on this page. Of course a malicious user
+ mentioned [262]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
@@ -2218,7 +2258,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 [261]-accept option that runs a program to examine
+ involves using the [263]-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
@@ -2247,11 +2287,11 @@ exit 1 # reject it
UsePrivilegeSeparation must be enabled.
- Q-36: I start x11vnc as root because it is launched via inetd(1) or a
+ Q-37: I start x11vnc as root because it is launched via inetd(1) or a
display manager like gdm(1). Can I have x11vnc later switch to a
different user?
- As of Feb/2005 x11vnc has the [262]-users option that allows things
+ As of Feb/2005 x11vnc has the [264]-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.
@@ -2260,7 +2300,7 @@ exit 1 # reject it
user nobody right after connections to the X display are established.
- Q-37: I use a screen-lock when I leave my workstation (e.g.
+ Q-38: I use a screen-lock when I leave my workstation (e.g.
xscreensaver or xlock). When I remotely access my workstation desktop
via x11vnc I can unlock the desktop fine, but I am worried people will
see my activities on the physical monitor. What can I do to prevent
@@ -2273,7 +2313,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 [263]blockdpy.c The idea behind it is simple (but
+ source for it is [265]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
@@ -2289,16 +2329,16 @@ 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 [264]-accept option and told
- to exit via the [265]-gone option (the vnc client user should
+ The blockdpy utility is launched by the [266]-accept option and told
+ to exit via the [267]-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.
- Q-38: Can I have x11vnc automatically lock the screen when I
+ Q-39: Can I have x11vnc automatically lock the screen when I
disconnect the VNC viewer?
- Yes, a user mentions he uses the [266]-gone option under CDE to run a
+ Yes, a user mentions he uses the [268]-gone option under CDE to run a
screen lock program:
x11vnc -display :0 -forever -gone 'dtaction LockDisplay'
@@ -2310,7 +2350,7 @@ exit 1 # reject it
[Display Managers and Services]
- Q-39: How can I run x11vnc as a "service" that is always available?
+ Q-40: How can I run x11vnc as a "service" that is always available?
There are a number of ways to do this. The primary thing you need to
decide is whether you want x11vnc to connect to the X session on the
@@ -2321,11 +2361,11 @@ exit 1 # reject it
need to have sufficient permissions to connect to the X display.
Here are some ideas:
- * Use the description under "Continuously" in the [267]FAQ on x11vnc
+ * Use the description under "Continuously" in the [269]FAQ on x11vnc
and Display Managers
- * Use the description in the [268]FAQ on x11vnc and inetd(1)
+ * Use the description in the [270]FAQ on x11vnc and inetd(1)
* Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc)
- * Although less reliable, see the [269]x11vnc_loop rc.local hack
+ * Although less reliable, see the [271]x11vnc_loop rc.local hack
below.
The display manager scheme will not be specific to which user has the
@@ -2344,7 +2384,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
plus any other options you desire.
- Q-40: How can I use x11vnc to connect to an X login screen like xdm,
+ Q-41: How can I use x11vnc to connect to an X login screen like xdm,
GNOME gdm, KDE kdm, or CDE dtlogin? (i.e. nobody is logged into an X
session yet).
@@ -2356,7 +2396,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 [270]-auth option sets the XAUTHORITY variable for you).
+ (the [272]-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
@@ -2381,7 +2421,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
- [271]the example at the end of this FAQ). Then restart dtlogin, e.g.:
+ [273]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
@@ -2444,7 +2484,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 [272]full details
+ killed immediately after the user logs in. Here are [274]full details
on how to configure gdm
_________________________________________________________________
@@ -2486,23 +2526,23 @@ 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: [273]x11vnc_loop It will need some local
+ file like rc.local: [275]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
- [274]this FAQ.
+ [276]this FAQ.
- Q-41: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
+ Q-42: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
Yes, perhaps a line something like this in /etc/inetd.conf will do it
for you:
5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh
- where the shell script /usr/local/bin/x11vnc_sh uses the [275]-inetd
+ where the shell script /usr/local/bin/x11vnc_sh uses the [277]-inetd
option and looks something like (you'll need to customize to your
settings).
#!/bin/sh
@@ -2515,7 +2555,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 [276]-quiet) option: "/usr/local/bin/x11vnc -q
+ specify the -q (aka [278]-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
@@ -2523,7 +2563,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 [277]-auth to point to the
+ Note also the need to set XAUTHORITY via [279]-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
@@ -2587,11 +2627,11 @@ service x11vncservice
capture a log)
- Q-42: How do I make x11vnc work with the Java VNC viewer applet in a
+ Q-43: How do I make x11vnc work with the Java VNC viewer applet in a
web browser?
To have x11vnc serve up a Java VNC viewer applet to any web browsers
- that connect to it, run x11vnc with this [278]option:
+ that connect to it, run x11vnc with this [280]option:
-httpdir /path/to/the/java/classes/dir
(this directory will contain the files index.vnc and, for example,
@@ -2610,7 +2650,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 [279]-http option will try to guess where the Java
+ As of May/2005 the [281]-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
@@ -2618,13 +2658,13 @@ service x11vncservice
either the java or appletviewer commands to run the program.
- Q-43: Are reverse connections (i.e. the VNC server connecting to the
+ Q-44: Are reverse connections (i.e. the VNC server connecting to the
VNC viewer) using "vncviewer -listen" and vncconnect(1) supported?
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 [280]-connect option. To connect immediately
+ starts up x11vnc with the [282]-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
@@ -2632,7 +2672,7 @@ service x11vncservice
hosts to connect to.
To use the vncconnect(1) program (from the core VNC package at
- www.realvnc.com) specify the [281]-vncconnect option to x11vnc (Note:
+ www.realvnc.com) specify the [283]-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
@@ -2646,7 +2686,7 @@ service x11vncservice
xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
- Q-44: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real
+ Q-45: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real
display, but for a virtual one I keep around).
You can, but you would not be doing this for performance reasons (for
@@ -2676,7 +2716,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
- [282]-add_keysyms option to have keysyms added automatically. Also, to
+ [284]-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"
@@ -2698,11 +2738,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) [283]switching even though it
+ Linux Virtual Console/Terminal (VC/VT) [285]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 [284]Xdummy that allows you to
+ Jul/2005 we have an LD_PRELOAD script [286]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
@@ -2722,7 +2762,7 @@ startx -- /path/to/Xdummy :1
testing x11vnc).
- Q-45: How can I use x11vnc on "headless" machines? Why might I want
+ Q-46: How can I use x11vnc on "headless" machines? Why might I want
to?
An interesting application of x11vnc is to let it export displays of
@@ -2734,7 +2774,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 [285]this FAQ) and access it from
+ display via x11vnc (e.g. see [287]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
@@ -2759,7 +2799,7 @@ startx -- /path/to/Xdummy :1
[Resource Usage and Performance]
- Q-46: I have lots of memory, but why does x11vnc fail with shmget:
+ Q-47: I have lots of memory, but why does x11vnc fail with shmget:
No space left on device or Minor opcode of failed request: 1
(X_ShmAttach)?
@@ -2777,7 +2817,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 [286]shm_clear to list and prompt for removal
+ Here is a shell script [288]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,
@@ -2811,40 +2851,40 @@ ied)
in /etc/system. See the next paragraph for more workarounds.
To minimize the number of shm segments used by x11vnc try using the
- [287]-onetile option (corresponds to only 3 shm segments used, and
+ [289]-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
- [288]-noshm option. Performance will be somewhat degraded but when
+ [290]-noshm option. Performance will be somewhat degraded but when
done over local machine sockets it should be acceptable (see an
- [289]earlier question discussing -noshm).
+ [291]earlier question discussing -noshm).
- Q-47: How can I make x11vnc use less system resources?
+ Q-48: How can I make x11vnc use less system resources?
- The [290]-nap and "[291]-wait n" (where n is the sleep between polls
+ The [292]-nap and "[293]-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
- [292]-onetile option will use less memory and use fewer shared memory
- slots (add [293]-fs 1.0 for one less slot).
+ [294]-onetile option will use less memory and use fewer shared memory
+ slots (add [295]-fs 1.0 for one less slot).
- Q-48: How can I make x11vnc use MORE system resources?
+ Q-49: How can I make x11vnc use MORE system resources?
- You can try [294]-threads and dial down the wait time (e.g. -wait 1)
- and possibly dial down [295]-defer as well. Note that if you try to
+ You can try [296]-threads and dial down the wait time (e.g. -wait 1)
+ and possibly dial down [297]-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 [296]-id option) can be streamed over a LAN or wireless at
+ the x11vnc [298]-id option) can be streamed over a LAN or wireless at
a reasonable frame rate.
- Q-49: I use x11vnc over a slow link with high latency (e.g. dialup
+ Q-50: I use x11vnc over a slow link with high latency (e.g. dialup
modem), is there anything I can do to speed things up?
Some things you might want to experiment with (many of which will help
@@ -2856,16 +2896,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
- [297]-solid [color] option to try to do this automatically.
+ [299]-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 [298]-scrollcopyrect is active and
+ problem in x11vnc 0.7.2 if [300]-scrollcopyrect is active and
detecting scrolls for the application).
- * If the [299]-wireframe option is not available (earlier than
+ * If the [301]-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)
@@ -2885,7 +2925,7 @@ ied)
noticed.
VNC viewer parameters:
- * Use a [300]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer
+ * Use a [302]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
@@ -2908,32 +2948,32 @@ ied)
file.
x11vnc parameters:
- * Try using [301]-nodragging (no screen updates when dragging mouse,
+ * Try using [303]-nodragging (no screen updates when dragging mouse,
but sometimes you miss visual feedback)
- * Make sure the [302]-wireframe option is active (it should be on by
+ * Make sure the [304]-wireframe option is active (it should be on by
default) and you have Opaque Moves/Resizes Enabled in the window
manager.
- * Make sure the [303]-scrollcopyrect option is active (it should be
+ * Make sure the [305]-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 [304]-fs 1.0 (disables fullscreen updates)
- * Try increasing [305]-wait or [306]-defer (reduces the maximum
+ * Set [306]-fs 1.0 (disables fullscreen updates)
+ * Try increasing [307]-wait or [308]-defer (reduces the maximum
"frame rate", but won't help much for large screen changes)
- * Try the [307]-progressive pixelheight mode with the block
+ * Try the [309]-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 [308]-id (cuts
+ * If you just want to watch one (simple) window use [310]-id (cuts
down extraneous polling and updates, but can be buggy or
insufficient)
- * Set [309]-nosel (disables all clipboard selection exchange)
- * Use [310]-nocursor and [311]-nocursorpos (repainting the remote
+ * Set [311]-nosel (disables all clipboard selection exchange)
+ * Use [312]-nocursor and [313]-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
- [312]-readtimeout n setting if it sometimes takes more than 20sec
+ [314]-readtimeout n setting if it sometimes takes more than 20sec
to paint the full screen, etc.
- Q-50: Does x11vnc support the X DAMAGE Xserver extension to find
+ Q-51: Does x11vnc support the X DAMAGE Xserver extension to find
modified regions of the screen quickly and efficiently?
Yes, as of Mar/2005 in the libvncserver CVS x11vnc will use the X
@@ -2951,7 +2991,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 [313]slow (e.g.
+ in main memory. So reading the fb is still painfully [315]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
@@ -2969,27 +3009,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 "[314]-xd_area A" option to adjust the size
+ skipped). You can use the "[316]-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 "[315]-xd_mem f" may also be of use in tuning the
- algorithm. To disable using DAMAGE entirely use "[316]-noxdamage".
+ The option "[317]-xd_mem f" may also be of use in tuning the
+ algorithm. To disable using DAMAGE entirely use "[318]-noxdamage".
- Q-51: When I drag windows around with the mouse or scroll up and down
+ Q-52: 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 [317]slow hardware read rates from
+ This problem is primarily due to [319]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
- [318]-pointer_mode option for more info. The next bottleneck is
+ [320]-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
@@ -2999,31 +3039,31 @@ 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 "[319]-pointer_mode 1" option.
+ way via the "[321]-pointer_mode 1" option.
- Also added was the [320]-nodragging option that disables all screen
+ Also added was the [322]-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 [321]-pointer_mode n option
+ As of Dec/2004 in the libvncserver CVS the [323]-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 [322]-threads option can improve
+ Also, in some circumstances the [324]-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
- [323]wireframe FAQ and [324]scrollcopyrect FAQ below) provide schemes
+ [325]wireframe FAQ and [326]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.
- Q-52: Why not do something like wireframe animations to avoid the
+ Q-53: Why not do something like wireframe animations to avoid the
windows "lurching" when being moved or resized?
Nice idea for a hack! As of Apr/2005 in the libvncserver CVS x11vnc by
@@ -3034,8 +3074,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 [325]slow video
- card read rates (see [326]here too). A displacement, even a small one,
+ of the intermediate steps. BTW the lurching is due to [327]slow video
+ card read rates (see [328]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.
@@ -3043,7 +3083,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 [327]-nowireframe option
+ with the problem. It can be disabled with the [329]-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
@@ -3088,13 +3128,13 @@ ied)
* Maximum time to show a wireframe animation.
* Minimum time between sending wireframe outlines.
- See the [328]"-wireframe tweaks" option for more details. On a slow
+ See the [330]"-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
- [329]"-wirecopyrect mode" option. It is also on by default. This
+ [331]"-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
@@ -3125,7 +3165,7 @@ ied)
-nowirecopyrect if this or other painting errors are unacceptable.
- Q-53: Can x11vnc try to apply heuristics to detect when an window is
+ Q-54: Can x11vnc try to apply heuristics to detect when an window is
scrolling its contents and use the CopyRect encoding for a speedup?
Another nice idea for a hack! As of May/2005 in the libvncserver CVS
@@ -3142,7 +3182,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 [330]slow).
+ the hardware framebuffer is [332]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.
@@ -3164,10 +3204,10 @@ ied)
the X server display: if one falls too far behind it could become a
mess...
- The initial implementation of [331]-scrollcopyrect option is useful in
+ The initial implementation of [333]-scrollcopyrect option is useful in
that it detects many scrolls and thus gives a much nicer working
- environment (especially when combined with the [332]-wireframe
- [333]-wirecopyrect [334]options, which are also on by default; and if
+ environment (especially when combined with the [334]-wireframe
+ [335]-wirecopyrect [336]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.
@@ -3200,10 +3240,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: [335]-fixscreen
+ also: [337]-fixscreen
* Some applications, notably OpenOffice, do XCopyArea scrolls in
weird ways that assume ancestor window clipping is taking place.
- See the [336]-scr_skip option for ways to tweak this on a
+ See the [338]-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
@@ -3220,7 +3260,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 [337]-scale option there will be a quick CopyRect
+ * When using the [339]-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
@@ -3233,7 +3273,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 [338]-noscrollcopyrect (or -noscr for short). If you find
+ with the [340]-noscrollcopyrect (or -noscr for short). If you find
some extremely bad and repeatable behavior for -scrollcopyrect please
report a bug.
@@ -3257,7 +3297,7 @@ ied)
[Mouse Cursor Shapes]
- Q-54: Why isn't the mouse cursor shape (the little icon shape where
+ Q-55: Why isn't the mouse cursor shape (the little icon shape where
the mouse pointer is) correct as I move from window to window?
On X servers supporting XFIXES or Solaris/IRIX Overlay extensions it
@@ -3272,16 +3312,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 "[339]-cursor X" option that
+ A simple kludge is provided by the "[341]-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 "[340]-cursor some" option for
+ work for those cases. Also see the "[342]-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 [341]-overlay option is supplied. See [342]this FAQ
+ cursor when the [343]-overlay option is supplied. See [344]this FAQ
for more info.
Also as of Dec/2004 in the libvncserver CVS XFIXES X extension support
@@ -3289,7 +3329,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 [343]Solaris 10.
+ distros and [345]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
@@ -3297,10 +3337,10 @@ 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. [344]Details can be found here.
+ hidden alpha channel data under 32bpp. [346]Details can be found here.
- Q-55: When using XFIXES cursorshape mode, some of the cursors look
+ Q-56: When using XFIXES cursorshape mode, some of the cursors look
really bad with extra black borders around the cursor and other cruft.
How can I improve their appearance?
@@ -3330,17 +3370,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 "[345]-alphacut n" option lets
+ course!) some tunable parameters. The "[347]-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 "[346]-alphafrac f" option tries to correct individual
+ 240. The "[348]-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 [347]-alpharemove that is useful for
+ Finally, there is an option [349]-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
@@ -3358,7 +3398,7 @@ ied)
heavily on redglass) look fine with the apparent default of alphacut:255.
- Q-56: In XFIXES mode, are there any hacks to handle cursor
+ Q-57: In XFIXES mode, are there any hacks to handle cursor
transparency ("alpha channel") exactly?
As of Jan/2005 in the CVS, libvncserver has been modified to allow an
@@ -3366,11 +3406,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 [348]-nocursorshape x11vnc option.
+ disabled for all clients with the [350]-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
- [349]-noalphablend option to disable this behavior (always approximate
+ [351]-noalphablend option to disable this behavior (always approximate
transparent cursors with opaque RGB values).
The CursorShapeUpdates VNC extension complicates matters because the
@@ -3395,12 +3435,12 @@ ied)
[Mouse Pointer]
- Q-57: Why does the mouse arrow just stay in one corner in my
+ Q-58: 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 [350]tightvnc extension
+ This default takes advantage of a [352]tightvnc extension
(CursorShapeUpdates) that allows specifying a cursor image shape for
- the local VNC viewer. You may disable it with the [351]-nocursor
+ the local VNC viewer. You may disable it with the [353]-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
@@ -3409,23 +3449,23 @@ ied)
framebuffer. This can also be disabled via -nocursor.
- Q-58: Can I take advantage of the TightVNC extension to the VNC
+ Q-59: Can I take advantage of the TightVNC extension to the VNC
protocol where Cursor Positions Updates are sent back to all connected
clients (i.e. passive viewers can see the mouse cursor being moved
around by another viewer)?
- Use the [352]-cursorpos option when starting x11vnc. A VNC viewer must
+ Use the [354]-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 [353]-nocursorpos
- and [354]-nocursorshape.
+ libvncserver CVS -cursorpos is the default. See also [355]-nocursorpos
+ and [356]-nocursorshape.
- Q-59: Is it possible to swap the mouse buttons (e.g. left-handed
+ Q-60: 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: [355]-buttonmap
+ You can remap the mouse buttons via something like: [357]-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.
@@ -3433,7 +3473,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 [356]-debug_pointer option prints out much info for
+ Note that the [358]-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
@@ -3455,7 +3495,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 [357]-buttonmap but rather configuring the X server
+ consider not using [359]-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"').
@@ -3482,10 +3522,10 @@ ied)
"click" usually gives a multi-line scroll).
[Keyboard Issues]
- Q-60: How can I get my AltGr and Shift modifiers to work between
+ Q-61: How can I get my AltGr and Shift modifiers to work between
keyboards for different languages?
- The option [358]-modtweak should help here. It is a mode that monitors
+ The option [360]-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.
@@ -3494,21 +3534,21 @@ 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 [359]this FAQ
+ and ">" it. This key does not exist on the keyboard (see [361]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 [360]FAQ about the -xkb option for a more powerful method
+ Also see the [362]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
- [361]-debug_keyboard option prints out much info for every keystroke
+ [363]-debug_keyboard option prints out much info for every keystroke
and so can be useful debugging things.
- Q-61: When I try to type a "<" (i.e. less than) instead I get ">"
+ Q-62: When I try to type a "<" (i.e. less than) instead I get ">"
(i.e. greater than)! Strangely, typing ">" works OK!!
Does your keyboard have a single key with both "<" and ">" on it? Even
@@ -3516,9 +3556,9 @@ ied)
(e.g. pc105 in the XF86Config file when it should be something else,
say pc104).
- Short Cut: Try the [362]-xkb or [363]-sloppy_keys options and see if
+ Short Cut: Try the [364]-xkb or [365]-sloppy_keys options and see if
that helps the situation. The discussion below is a bit outdated (e.g.
- [364]-modtweak is now the default) but is useful reference for various
+ [366]-modtweak is now the default) but is useful reference for various
tricks and so is kept.
@@ -3561,34 +3601,34 @@ ied)
-remap less-comma
These are convenient in that they do not modify the actual X server
- settings. The former ([365]-modtweak) is a mode that monitors the
+ settings. The former ([367]-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 ([366]-remap less-comma) is an immediate remapping of the
+ The latter ([368]-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 [367]FAQ about the -xkb option as a possible workaround
+ See also the [369]FAQ about the -xkb option as a possible workaround
using the XKEYBOARD extension.
- Note that the [368]-debug_keyboard option prints out much info for
+ Note that the [370]-debug_keyboard option prints out much info for
every keystroke to aid debugging keyboard problems.
- Q-62: When I try to type a "<" (i.e. less than) instead I get "<,"
+ Q-63: When I try to type a "<" (i.e. less than) instead I get "<,"
(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 [369]keymapping
+ the Shift key before releasing the "<". Because of a [371]keymapping
ambiguity the last event "< up" is interpreted as "," because that key
unshifted is the comma.
- This should not happen in [370]-xkb mode, because it works hard to
+ This should not happen in [372]-xkb mode, because it works hard to
resolve the ambiguities. If you do not want to use -xkb, try the
- option [371]-sloppy_keys to attempt a similar type of algorithm.
+ option [373]-sloppy_keys to attempt a similar type of algorithm.
- Q-63: I'm using an "international" keyboard (e.g. German "de", or
+ Q-64: I'm using an "international" keyboard (e.g. German "de", or
Danish "dk") and the -modtweak mode works well if the VNC viewer is
run on a Unix/Linux machine with a similar keyboard. But if I run
the VNC viewer on Unix/Linux with a different keyboard (e.g. "us") or
@@ -3609,7 +3649,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 [372]-modtweak
+ This all worked fine with x11vnc running with the [374]-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
@@ -3627,7 +3667,7 @@ ied)
* there is a new option -xkb to use the XKEYBOARD extension API to
do the Modifier key tweaking.
- The [373]-xkb option seems to fix all of the missing keys: "@", "<",
+ The [375]-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
@@ -3635,7 +3675,7 @@ ied)
debugging output (send it along with any problems you report).
Update: as of Jun/2005 x11vnc will try to automatically enable
- [374]-xkb if it appears that would be beneficial (e.g. if it sees any
+ [376]-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.
@@ -3650,7 +3690,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:
- [375]-skip_keycodes 93
+ [377]-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
@@ -3667,16 +3707,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 [376]-remap x11vnc option:
+ created using the [378]-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
- [377]-add_keysyms option in the next paragraph.
- Update: for convenience "[378]-remap DEAD" does many of these
+ [379]-add_keysyms option in the next paragraph.
+ Update: for convenience "[380]-remap DEAD" does many of these
mappings at once.
- * To complement the above workaround using the [379]-remap, an
- option [380]-add_keysyms was added. This option instructs x11vnc
+ * To complement the above workaround using the [381]-remap, an
+ option [382]-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
@@ -3687,7 +3727,7 @@ ied)
disable.
- Q-64: When typing I sometimes get double, triple, or more of my
+ Q-65: When typing I sometimes get double, triple, or more of my
keystrokes repeated. I'm sure I only typed them once, what can I do?
This may be due to an interplay between your X server's key autorepeat
@@ -3695,7 +3735,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) [381]-norepeat x11vnc option. You will still
+ use the new (Jul/2004) [383]-norepeat x11vnc option. You will still
have autorepeating because that is taken care of on your VNC viewer
side.
@@ -3719,18 +3759,18 @@ 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 [382]-norepeat (which has since Dec/2004 been
+ needed, or to use the [384]-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
working at the physical display and misses his autorepeating.
- Q-65: The x11vnc -norepeat mode is in effect, but I still get repeated
+ Q-66: The x11vnc -norepeat mode is in effect, but I still get repeated
keystrokes!!
Are you using x11vnc to log in to an X session? (as described in
- [383]this FAQ) If so, x11vnc is starting before your session and it
+ [385]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
@@ -3750,11 +3790,11 @@ ied)
should figure out how to disable that somehow.
- Q-66: The machine where I run x11vnc has an AltGr key, but the local
+ Q-67: The machine where I run x11vnc has an AltGr key, but the local
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 "[384]-remap Super_R-Mode_switch" x11vnc option may
+ Something like "[386]-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)).
@@ -3765,7 +3805,7 @@ ied)
specify remappings from a file.
- Q-67: I have a Sun machine I run x11vnc on. Its Sun keyboard has just
+ Q-68: I have a Sun machine I run x11vnc on. Its Sun keyboard has just
one Alt key labelled "Alt" and two Meta keys labelled with little
diamonds. The machine where I run the VNC viewer only has Alt keys.
How can I send a Meta keypress? (e.g. emacs needs this)
@@ -3777,18 +3817,18 @@ 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 [385]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
+ the [387]-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.
- Q-68: Can I map a keystroke to a mouse button click on the remote
+ Q-69: Can I map a keystroke to a mouse button click on the remote
machine?
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 [386]-remap
+ have x11vnc do the remapping. This can be done via the [388]-remap
option using the fake "keysyms" Button1, Button2, etc. as the "to"
keys (i.e. the ones after the "-")
@@ -3797,7 +3837,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:
- [387]-remap Super_R-Button2
+ [389]-remap Super_R-Button2
maps the Super_R "flag" key press to the Button2 click, thereby making
X pasting a bit easier.
@@ -3808,7 +3848,7 @@ ied)
[Screen Related Issues and Features]
- Q-69: The remote display is larger (in number of pixels) than the
+ Q-70: The remote display is larger (in number of pixels) than the
local display I am running the vncviewer on. I don't like the
vncviewer scrollbars, what I can do?
@@ -3827,15 +3867,15 @@ 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
- [388]this FAQ on x11vnc scaling.
+ [390]this FAQ on x11vnc scaling.
- Q-70: Does x11vnc support server-side framebuffer scaling? (E.g. to
+ Q-71: Does x11vnc support server-side framebuffer scaling? (E.g. to
make the desktop smaller).
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 "[389]-scale fraction"
+ per-client setting. To enable it use the "[391]-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.
@@ -3856,7 +3896,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
- [390]applications. Since with integer scale factors the framebuffers
+ [392]applications. Since with integer scale factors the framebuffers
become huge and scaling operations time consuming, be sure to use
":nb" for the fastest response.
@@ -3882,12 +3922,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 ([391]-rfbport option,
+ different scalings listening on separate ports ([393]-rfbport option,
etc.).
BTW, whenever you run two or more x11vnc's on the same X display and
- use the [392]GUI, then to avoid all of the x11vnc's simultaneously
- answering the gui you will need to use something like [393]"-connect
+ use the [394]GUI, then to avoid all of the x11vnc's simultaneously
+ answering the gui you will need to use something like [395]"-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
@@ -3896,12 +3936,12 @@ 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 [394]"-scale_cursor frac" option to set the cursor
+ want that, use the [396]"-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).
- Q-71: Does x11vnc work with Xinerama? (i.e. multiple monitors joined
+ Q-72: Does x11vnc work with Xinerama? (i.e. multiple monitors joined
together to form one big, single screen).
Yes, it should generally work because it simply polls the big
@@ -3918,23 +3958,23 @@ 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 [395]-blackout x11vnc option
+ may be distracting to the viewer. The [397]-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
- [396]-xinerama x11vnc option can be used to have it automatically
+ [398]-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 [397]-xwarppointer
+ of the large display. If this happens try using the [399]-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
Xinerama is enabled).
- Q-72: Can I use x11vnc on a multi-headed display that is not Xinerama
+ Q-73: Can I use x11vnc on a multi-headed display that is not Xinerama
(i.e. separate screens :0.0, :0.1, ... for each monitor)?
You can, but it is a little bit awkward: you must start separate
@@ -3952,32 +3992,32 @@ 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 [398]FAQ to increase the limit. It
- is probably also a good idea to run with the [399]-onetile option in
+ /etc/system as mentioned in another [400]FAQ to increase the limit. It
+ is probably also a good idea to run with the [401]-onetile option in
this case (to limit each x11vnc to 3 shm segments), or even
- [400]-noshm to use no shm segments.
+ [402]-noshm to use no shm segments.
- Q-73: Can x11vnc show only a portion of the display? (E.g. for a
+ Q-74: 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 "[401]-clip
+ As of Mar/2005 in the libvncserver CVS x11vnc has the "[403]-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 [402]Xinerama screen into two more managable smaller screens.
+ large [404]Xinerama screen into two more managable smaller screens.
This also works to view a sub-region of a single application window if
- the [403]-id or [404]-sid options are used. The offset is measured
+ the [405]-id or [406]-sid options are used. The offset is measured
from the upper left corner of the selected window.
- Q-74: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection)
+ Q-75: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection)
extension? Whenever I rotate or resize the screen x11vnc just seems to
crash.
As of Dec/2004 in the libvncserver CVS x11vnc supports XRANDR. You
- enable it with the [405]-xrandr option to make x11vnc monitor XRANDR
+ enable it with the [407]-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.
@@ -3987,7 +4027,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 [406]-padgeom option to make the region big
+ viewers you can try the [408]-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
@@ -3996,13 +4036,13 @@ ied)
terminate.
- Q-75: Why is the view in my VNC viewer completely black? Or why is
+ Q-76: Why is the view in my VNC viewer completely black? Or why is
everything flashing around randomly?
See the next FAQ for a possible explanation.
- Q-76: I use Linux Virtual Consoles (VC's) to implement 'Fast User
+ Q-77: I use Linux Virtual Consoles (VC's) to implement 'Fast User
Switching' between users' sessions (e.g. Betty is on Ctrl-Alt-F7,
Bobby is on Ctrl-Alt-F8, and Sid is on Ctrl-Alt-F1: they use those
keystrokes to switch between their sessions). How come the view in a
@@ -4030,7 +4070,7 @@ ied)
"chvt 7" for VC #7.
- Q-77: Can I use x11vnc to view my VMWare session remotely?
+ Q-78: Can I use x11vnc to view my VMWare session remotely?
Yes, since VMWare is an X application you can view it via x11vnc in
the normal way.
@@ -4041,9 +4081,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 [407]this FAQ
+ desktop in a separate Virtual Console (e.g. VC 8) (see [409]this FAQ
on VC's for background). Unfortunately, this Fullscreen VC is not an X
- server. So x11vnc cannot access it (however, [408]see this for a
+ server. So x11vnc cannot access it (however, [410]see this for a
possible partial workaround). x11vnc works fine with "Normal X
application window" and "Quick-Switch mode" because these use X.
@@ -4060,13 +4100,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 [409]is in the active VC.
+ as long as the VMWare X session [411]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 [410]-id windowid option. The
+ the VMWare menu buttons) by use of the [412]-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
@@ -4075,7 +4115,7 @@ ied)
mouse)).
- Q-78: Can non-X devices (e.g. a raw framebuffer) be viewed and/or
+ Q-79: Can non-X devices (e.g. a raw framebuffer) be viewed and/or
controlled by x11vnc?
As of Apr/2005 in the libvncserver CVS there is rudimentary support
@@ -4147,7 +4187,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 [411]X API, but you get
+ of Xvfb x11vnc can poll it much better via the [413]X API, but you get
the idea.
By default in -rawfb mode x11vnc will actually close any X display it
@@ -4200,7 +4240,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 [412]active VC) one
+ view and interact with VC #2 (assuming it is the [414]active VC) one
can run something like:
x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2'
@@ -4213,7 +4253,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
- [413]VMWare Fullscreen mode is actually viewable under -rawfb. But
+ [415]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...
@@ -4224,7 +4264,7 @@ ied)
program that passes the framebuffer to libvncserver.
- Q-79: I am using x11vnc where my local machine has "popup/hidden
+ Q-80: I am using x11vnc where my local machine has "popup/hidden
taskbars" (e.g. GNOME or MacOS X) and the remote display where x11vnc
runs also has "popup/hidden taskbars" (e.g. GNOME). When I move the
mouse to the edge of the screen where the popups happen, the taskbars
@@ -4239,23 +4279,23 @@ ied)
[Misc: Clipboard, Beeps, Thanks, etc.]
- Q-80: Does the Clipboard/Selection get transferred between the
+ Q-81: Does the Clipboard/Selection get transferred between the
vncviewer and the X display?
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 [414]-nosel option. If you
+ the Clipboard/Selection exchanged use the [416]-nosel option. If you
don't want the PRIMARY selection to be polled for changes use the
- [415]-noprimary option. You can also fine-tune it a bit with the
- [416]-seldir dir option.
+ [417]-noprimary option. You can also fine-tune it a bit with the
+ [418]-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
cutbuffers.
- Q-81: Why don't I hear the "Beeps" in my X session (e.g. when typing
+ Q-82: Why don't I hear the "Beeps" in my X session (e.g. when typing
tput bel in an xterm)?
As of Dec/2003 in the libvncserver CVS "Beep" XBell events are tracked
@@ -4263,7 +4303,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 [417]-nobell option. If
+ If you don't want to hear the beeps use the [419]-nobell option. If
you want to hear the audio from the remote applications, consider
trying a redirector such as esd.
@@ -4272,14 +4312,14 @@ ied)
Contributions:
- Q-82: Thanks for your program and for your help! Can I make a
+ Q-83: Thanks for your program and for your help! Can I make a
donation?
Please do (any amount is appreciated) and thank you for your support!
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
- [418]email!
+ [420]email!
[PayPal]
@@ -4387,322 +4427,324 @@ References
100. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg
101. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control
102. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 103. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 104. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt
- 105. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared
- 106. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
- 107. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 108. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface
- 109. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost
- 110. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix
- 111. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty
- 112. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
- 113. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
- 114. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt
- 115. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy
- 116. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock
- 117. http://www.karlrunge.com/x11vnc/index.html#faq-service
- 118. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 119. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 120. http://www.karlrunge.com/x11vnc/index.html#faq-java-http
- 121. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect
- 122. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 123. http://www.karlrunge.com/x11vnc/index.html#faq-headless
- 124. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 125. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource
- 126. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource
- 127. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link
- 128. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage
- 129. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
- 130. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 131. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
- 132. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape
- 133. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha
- 134. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 135. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow
- 136. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions
- 137. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt
- 138. http://www.karlrunge.com/x11vnc/index.html#faq-altgr
- 139. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 140. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless-sloppy
- 141. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 142. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys
- 143. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still
- 144. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt
- 145. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta
- 146. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click
- 147. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars
- 148. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 149. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
- 150. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen
- 151. http://www.karlrunge.com/x11vnc/index.html#faq-clip-screen
- 152. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr
- 153. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen
- 154. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 155. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
- 156. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
- 157. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars
- 158. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard
- 159. http://www.karlrunge.com/x11vnc/index.html#faq-beeps
- 160. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
- 161. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 162. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 163. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 164. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 165. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 166. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
- 167. http://www.karlrunge.com/x11vnc/index.html#building
- 168. http://www.karlrunge.com/x11vnc/index.html#faq-build
- 169. http://packages.debian.org/x11vnc
- 170. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
- 171. http://dag.wieers.com/packages/x11vnc/
- 172. http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Network/x11vnc/
- 173. http://www.sunfreeware.com/
- 174. http://www.bell-labs.com/project/wwexptools/packages.html
- 175. http://www.karlrunge.com/x11vnc/bins
- 176. http://www.tightvnc.com/download.html
- 177. http://www.realvnc.com/download-free.html
- 178. http://sourceforge.net/projects/cotvnc/
- 179. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
- 180. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 181. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
- 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
- 185. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
- 187. http://fredrik.hubbe.net/x2vnc.html
- 188. http://www.hubbe.net/~hubbe/win2vnc.html
- 189. http://www.deboer.gmxhome.de/
- 190. http://sourceforge.net/projects/win2vnc/
- 191. http://fredrik.hubbe.net/x2vnc.html
- 192. http://freshmeat.net/projects/x2x/
- 193. http://ftp.digital.com/pub/Digital/SRC/x2x/
- 194. http://zapek.com/software/zvnc/
- 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
- 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
- 198. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
- 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 103. http://www.karlrunge.com/x11vnc/index.html#faq-passwd-noecho
+ 104. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 105. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt
+ 106. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared
+ 107. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
+ 108. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 109. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface
+ 110. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost
+ 111. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix
+ 112. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty
+ 113. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
+ 114. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
+ 115. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt
+ 116. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy
+ 117. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock
+ 118. http://www.karlrunge.com/x11vnc/index.html#faq-service
+ 119. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 120. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 121. http://www.karlrunge.com/x11vnc/index.html#faq-java-http
+ 122. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect
+ 123. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 124. http://www.karlrunge.com/x11vnc/index.html#faq-headless
+ 125. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 126. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource
+ 127. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource
+ 128. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link
+ 129. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage
+ 130. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 131. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 132. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
+ 133. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape
+ 134. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha
+ 135. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 136. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow
+ 137. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions
+ 138. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt
+ 139. http://www.karlrunge.com/x11vnc/index.html#faq-altgr
+ 140. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 141. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless-sloppy
+ 142. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 143. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys
+ 144. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still
+ 145. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt
+ 146. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta
+ 147. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click
+ 148. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars
+ 149. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 150. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
+ 151. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen
+ 152. http://www.karlrunge.com/x11vnc/index.html#faq-clip-screen
+ 153. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr
+ 154. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen
+ 155. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 156. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
+ 157. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 158. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars
+ 159. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard
+ 160. http://www.karlrunge.com/x11vnc/index.html#faq-beeps
+ 161. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
+ 162. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 163. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 164. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 165. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 166. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 167. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
+ 168. http://www.karlrunge.com/x11vnc/index.html#building
+ 169. http://www.karlrunge.com/x11vnc/index.html#faq-build
+ 170. http://packages.debian.org/x11vnc
+ 171. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
+ 172. http://dag.wieers.com/packages/x11vnc/
+ 173. http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Network/x11vnc/
+ 174. http://www.sunfreeware.com/
+ 175. http://www.bell-labs.com/project/wwexptools/packages.html
+ 176. http://www.karlrunge.com/x11vnc/bins
+ 177. http://www.tightvnc.com/download.html
+ 178. http://www.realvnc.com/download-free.html
+ 179. http://sourceforge.net/projects/cotvnc/
+ 180. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
+ 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 182. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
+ 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
+ 186. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
+ 188. http://fredrik.hubbe.net/x2vnc.html
+ 189. http://www.hubbe.net/~hubbe/win2vnc.html
+ 190. http://www.deboer.gmxhome.de/
+ 191. http://sourceforge.net/projects/win2vnc/
+ 192. http://fredrik.hubbe.net/x2vnc.html
+ 193. http://freshmeat.net/projects/x2x/
+ 194. http://ftp.digital.com/pub/Digital/SRC/x2x/
+ 195. http://zapek.com/software/zvnc/
+ 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
+ 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
+ 199. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 203. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
- 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
- 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
- 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 210. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
- 211. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 212. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
- 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
- 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
- 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 223. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
- 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
- 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
- 231. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 232. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 233. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 236. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 237. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
- 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 204. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
+ 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
+ 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 211. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
+ 212. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
+ 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
+ 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 223. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 224. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
+ 227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
+ 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
+ 233. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 234. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 235. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 238. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 239. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
- 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 246. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 247. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 251. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh
- 252. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
- 256. ftp://ftp.x.org/
- 257. http://www.karlrunge.com/x11vnc/dtVncPopup
- 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 260. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 263. http://www.karlrunge.com/x11vnc/blockdpy.c
- 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 267. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 268. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 269. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
- 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 271. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
- 272. http://www.jirka.org/gdm-documentation/x241.html
- 273. http://www.karlrunge.com/x11vnc/x11vnc_loop
- 274. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
- 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
- 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 283. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 284. http://www.karlrunge.com/x11vnc/Xdummy
- 285. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 286. http://www.karlrunge.com/x11vnc/shm_clear
- 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 289. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
- 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 300. http://www.tightvnc.com/
- 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
- 308. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
- 313. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
- 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
- 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 317. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 248. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 249. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 253. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh
+ 254. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
+ 258. ftp://ftp.x.org/
+ 259. http://www.karlrunge.com/x11vnc/dtVncPopup
+ 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 262. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 265. http://www.karlrunge.com/x11vnc/blockdpy.c
+ 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 269. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 270. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 271. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
+ 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 273. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
+ 274. http://www.jirka.org/gdm-documentation/x241.html
+ 275. http://www.karlrunge.com/x11vnc/x11vnc_loop
+ 276. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
+ 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
+ 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
+ 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 285. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 286. http://www.karlrunge.com/x11vnc/Xdummy
+ 287. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 288. http://www.karlrunge.com/x11vnc/shm_clear
+ 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 291. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
+ 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 302. http://www.tightvnc.com/
+ 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 308. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
+ 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
+ 315. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
+ 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
+ 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 319. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 323. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 324. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
- 325. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
- 326. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 325. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 326. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
+ 327. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 328. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 330. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
- 334. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
- 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 342. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
- 343. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
- 344. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
- 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
- 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
- 348. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
- 350. http://www.tightvnc.com/
- 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
- 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 354. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 332. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
+ 336. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
+ 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 344. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
+ 345. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
+ 346. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
+ 348. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
+ 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
+ 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
+ 352. http://www.tightvnc.com/
+ 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 354. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
+ 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 359. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 360. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 361. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 363. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 364. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 366. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 367. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 368. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 369. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 371. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 372. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 375. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
- 376. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 377. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 360. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 361. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 362. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 363. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 364. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 366. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 367. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 368. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 369. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 371. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 372. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 375. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 376. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 377. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
378. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 379. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 380. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 381. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 382. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 383. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 384. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 385. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 379. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 380. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 381. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 382. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 383. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 384. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 385. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
386. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
387. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 388. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 389. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 390. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
- 391. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 392. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
- 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
- 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
- 398. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
- 402. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
- 403. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 404. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 405. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
- 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
- 407. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 408. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 388. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 389. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 390. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 391. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 392. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
+ 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
+ 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
+ 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
+ 400. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 402. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 403. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
+ 404. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
+ 405. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 407. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
+ 408. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
409. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 411. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 412. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 413. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
- 414. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
- 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
- 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
- 418. mailto:xvml@karlrunge.com
+ 410. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 411. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 412. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 413. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 414. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 415. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
+ 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
+ 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
+ 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
+ 420. mailto:xvml@karlrunge.com
=======================================================================
@@ -4715,7 +4757,7 @@ x11vnc: a VNC server for real X displays
Here are all of x11vnc command line options:
% x11vnc -opts (see below for -help long descriptions)
-x11vnc: allow VNC connections to real X11 displays. 0.7.3 lastmod: 2005-10-22
+x11vnc: allow VNC connections to real X11 displays. 0.7.3 lastmod: 2005-11-28
x11vnc options:
-display disp -auth file
@@ -4726,73 +4768,74 @@ x11vnc options:
-overlay_nocursor -scale fraction
-scale_cursor frac -viewonly
-shared -once
- -forever -timeout n
- -inetd -filexfer
- -http -connect string
- -vncconnect -novncconnect
- -allow host1[,host2..] -localhost
- -nolookup -input string
- -viewpasswd string -passwdfile filename
- -nopw -storepasswd pass file
- -accept string -gone string
- -users list -noshm
- -flipbyteorder -onetile
- -solid [color] -blackout string
- -xinerama -xtrap
- -xrandr [mode] -padgeom WxH
- -o logfile -flag file
- -rc filename -norc
- -h, -help -?, -opts
- -V, -version -dbg
- -q -bg
- -modtweak -nomodtweak
- -xkb -noxkb
- -skip_keycodes string -sloppy_keys
- -skip_dups -noskip_dups
- -add_keysyms -noadd_keysyms
- -clear_mods -clear_keys
- -remap string -norepeat
- -repeat -nofb
- -nobell -nosel
- -noprimary -seldir string
- -cursor [mode] -nocursor
- -arrow n -noxfixes
- -alphacut n -alphafrac fraction
- -alpharemove -noalphablend
- -nocursorshape -cursorpos
- -nocursorpos -xwarppointer
- -buttonmap string -nodragging
- -wireframe [str] -nowireframe
- -wirecopyrect mode -nowirecopyrect
- -debug_wireframe -scrollcopyrect mode
- -noscrollcopyrect -scr_area n
- -scr_skip list -scr_inc list
- -scr_keys list -scr_term list
- -scr_keyrepeat lo-hi -scr_parms string
- -fixscreen string -debug_scroll
- -noxrecord -grab_buster
- -nograb_buster -debug_grabs
- -pointer_mode n -input_skip n
- -speeds rd,bw,lat -wmdt string
- -debug_pointer -debug_keyboard
- -defer time -wait time
- -wait_ui factor -nowait_bog
- -slow_fb time -readtimeout n
- -nap -nonap
- -sb time -noxdamage
- -xd_area A -xd_mem f
- -sigpipe string -threads
- -nothreads -fs f
- -gaps n -grow n
- -fuzz n -debug_tiles
- -snapfb -rawfb string
- -pipeinput cmd -gui [gui-opts]
- -remote command -query variable
- -QD variable -sync
- -noremote -yesremote
- -unsafe -safer
- -privremote -nocmds
- -deny_all
+ -forever -loop
+ -timeout n -inetd
+ -filexfer -http
+ -connect string -vncconnect
+ -novncconnect -allow host1[,host2..]
+ -localhost -nolookup
+ -input string -viewpasswd string
+ -passwdfile filename -nopw
+ -storepasswd pass file -accept string
+ -gone string -users list
+ -noshm -flipbyteorder
+ -onetile -solid [color]
+ -blackout string -xinerama
+ -xtrap -xrandr [mode]
+ -padgeom WxH -o logfile
+ -flag file -rc filename
+ -norc -h, -help
+ -?, -opts -V, -version
+ -dbg -q
+ -bg -modtweak
+ -nomodtweak -xkb
+ -noxkb -skip_keycodes string
+ -sloppy_keys -skip_dups
+ -noskip_dups -add_keysyms
+ -noadd_keysyms -clear_mods
+ -clear_keys -remap string
+ -norepeat -repeat
+ -nofb -nobell
+ -nosel -noprimary
+ -seldir string -cursor [mode]
+ -nocursor -arrow n
+ -noxfixes -alphacut n
+ -alphafrac fraction -alpharemove
+ -noalphablend -nocursorshape
+ -cursorpos -nocursorpos
+ -xwarppointer -buttonmap string
+ -nodragging -wireframe [str]
+ -nowireframe -wirecopyrect mode
+ -nowirecopyrect -debug_wireframe
+ -scrollcopyrect mode -noscrollcopyrect
+ -scr_area n -scr_skip list
+ -scr_inc list -scr_keys list
+ -scr_term list -scr_keyrepeat lo-hi
+ -scr_parms string -fixscreen string
+ -debug_scroll -noxrecord
+ -grab_buster -nograb_buster
+ -debug_grabs -pointer_mode n
+ -input_skip n -speeds rd,bw,lat
+ -wmdt string -debug_pointer
+ -debug_keyboard -defer time
+ -wait time -wait_ui factor
+ -nowait_bog -slow_fb time
+ -readtimeout n -nap
+ -nonap -sb time
+ -noxdamage -xd_area A
+ -xd_mem f -sigpipe string
+ -threads -nothreads
+ -fs f -gaps n
+ -grow n -fuzz n
+ -debug_tiles -snapfb
+ -rawfb string -pipeinput cmd
+ -gui [gui-opts] -remote command
+ -query variable -QD variable
+ -sync -noremote
+ -yesremote -unsafe
+ -safer -privremote
+ -nocmds -deny_all
+
libvncserver options:
-rfbport port TCP port for RFB protocol
@@ -4818,7 +4861,7 @@ libvncserver options:
% x11vnc -help
-x11vnc: allow VNC connections to real X11 displays. 0.7.3 lastmod: 2005-10-22
+x11vnc: allow VNC connections to real X11 displays. 0.7.3 lastmod: 2005-11-28
Typical usage is:
@@ -4992,6 +5035,14 @@ Options:
disconnects, opposite of -forever. This is the Default.
-forever Keep listening for more connections rather than exiting
as soon as the first client(s) disconnect. Same as -many
+-loop Create an outer loop restarting the x11vnc process
+ whenever it terminates. -bg and -inetd are ignored in
+ this mode. Useful for continuing even if the X server
+ terminates and restarts (you will need permission to
+ reconnect of course). Use, e.g., -loop100 to sleep
+ 100 millisecs between restarts, etc. Default is 2000ms
+ (i.e. 2 secs) Use, e.g. -loop300,5 to sleep 300 ms
+ and only loop 5 times.
-timeout n Exit unless a client connects within the first n seconds
after startup.
-inetd Launched by inetd(1): stdio instead of listening socket.
diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1
index d112da9..383bd9c 100644
--- a/x11vnc/x11vnc.1
+++ b/x11vnc/x11vnc.1
@@ -1,8 +1,8 @@
.\" This file was automatically generated from x11vnc -help output.
-.TH X11VNC "1" "October 2005" "x11vnc " "User Commands"
+.TH X11VNC "1" "November 2005" "x11vnc " "User Commands"
.SH NAME
x11vnc - allow VNC connections to real X11 displays
- version: 0.7.3, lastmod: 2005-10-22
+ version: 0.7.3, lastmod: 2005-11-28
.SH SYNOPSIS
.B x11vnc
[OPTION]...
@@ -237,6 +237,17 @@ disconnects, opposite of \fB-forever.\fR This is the Default.
Keep listening for more connections rather than exiting
as soon as the first client(s) disconnect. Same as \fB-many\fR
.PP
+\fB-loop\fR
+.IP
+Create an outer loop restarting the x11vnc process
+whenever it terminates. \fB-bg\fR and \fB-inetd\fR are ignored in
+this mode. Useful for continuing even if the X server
+terminates and restarts (you will need permission to
+reconnect of course). Use, e.g., \fB-loop100\fR to sleep
+100 millisecs between restarts, etc. Default is 2000ms
+(i.e. 2 secs) Use, e.g. \fB-loop300,5\fR to sleep 300 ms
+and only loop 5 times.
+.PP
\fB-timeout\fR \fIn\fR
.IP
Exit unless a client connects within the first n seconds
diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c
index 2fb2115..9987ed8 100644
--- a/x11vnc/x11vnc.c
+++ b/x11vnc/x11vnc.c
@@ -398,7 +398,7 @@ double xdamage_scheduled_mark = 0.0;
sraRegionPtr xdamage_scheduled_mark_region = NULL;
/* date +'lastmod: %Y-%m-%d' */
-char lastmod[] = "0.7.3 lastmod: 2005-11-25";
+char lastmod[] = "0.7.3 lastmod: 2005-11-28";
int hack_val = 0;
/* X display info */
@@ -23530,7 +23530,7 @@ static void nap_set(int tile_cnt) {
if(now > last_fb_bytes_sent + no_fbu_blank) {
if (debug_tiles > 1) {
printf("nap_set: nap_ok=1: now: %d last: %d\n",
- now, last_fb_bytes_sent);
+ (int) now, (int) last_fb_bytes_sent);
}
nap_ok = 1;
}
@@ -29809,8 +29809,8 @@ void record_last_fb_update(void) {
if (rbs != rbs0) {
rbs0 = rbs;
if (debug_tiles > 1) {
- printf("record_last_fb_update: %d %d\n", now,
- last_fb_bytes_sent);
+ printf("record_last_fb_update: %d %d\n",
+ (int) now, (int) last_fb_bytes_sent);
}
last_fb_bytes_sent = now;
}
@@ -30328,6 +30328,14 @@ static void print_help(int mode) {
" disconnects, opposite of -forever. This is the Default.\n"
"-forever Keep listening for more connections rather than exiting\n"
" as soon as the first client(s) disconnect. Same as -many\n"
+"-loop Create an outer loop restarting the x11vnc process\n"
+" whenever it terminates. -bg and -inetd are ignored in\n"
+" this mode. Useful for continuing even if the X server\n"
+" terminates and restarts (you will need permission to\n"
+" reconnect of course). Use, e.g., -loop100 to sleep\n"
+" 100 millisecs between restarts, etc. Default is 2000ms\n"
+" (i.e. 2 secs) Use, e.g. -loop300,5 to sleep 300 ms\n"
+" and only loop 5 times.\n"
"-timeout n Exit unless a client connects within the first n seconds\n"
" after startup.\n"
"-inetd Launched by inetd(1): stdio instead of listening socket.\n"
@@ -32873,6 +32881,83 @@ void nopassword_warning_msg(int gotloc) {
#endif
}
+void check_loop_mode(int argc, char* argv[]) {
+ int i;
+ int loop_mode = 0, loop_sleep = 2000, loop_max = 0;
+
+ for (i=1; i < argc; i++) {
+ char *p = argv[i];
+ if (strstr(p, "--") == p) {
+ p++;
+ }
+ if (strstr(p, "-loop") == p) {
+ char *q;
+ loop_mode = 1;
+ if ((q = strchr(p, ',')) != NULL) {
+ loop_max = atoi(q+1);
+ *q = '\0';
+ }
+
+ q = strpbrk(p, "0123456789");
+ if (q) {
+ loop_sleep = atoi(q);
+ if (loop_sleep <= 0) {
+ loop_sleep = 10;
+ }
+ }
+ }
+ }
+ if (loop_mode && getenv("X11VNC_LOOP_MODE") == NULL) {
+#if LIBVNCSERVER_HAVE_FORK
+ char **argv2;
+ int k, i = 1;
+
+ set_env("X11VNC_LOOP_MODE", "1");
+ argv2 = (char **) malloc((argc+1)*sizeof(char *));
+
+ for (k=0; k < argc+1; k++) {
+ argv2[k] = NULL;
+ if (k < argc) {
+ argv2[k] = argv[k];
+ }
+ }
+ while (1) {
+ int status;
+ pid_t p;
+ fprintf(stderr, "\n --- x11vnc loop: %d ---\n\n", i++);
+ fflush(stderr);
+ usleep(500 * 1000);
+ if ((p = fork()) > 0) {
+ fprintf(stderr, " --- x11vnc loop: waiting "
+ "for: %d\n\n", p);
+ wait(&status);
+ } else if (p == -1) {
+ fprintf(stderr, "could not fork\n");
+ perror("fork");
+ exit(1);
+ } else {
+ execvp(argv[0], argv2);
+ exit(1);
+ }
+
+ if (loop_max > 0 && i > loop_max) {
+ fprintf(stderr, "\n --- x11vnc loop: did %d"
+ " done. ---\n\n", loop_max);
+ break;
+ }
+
+ fprintf(stderr, "\n --- x11vnc loop: sleeping %d ms "
+ "---\n\n", loop_sleep);
+ usleep(loop_sleep * 1000);
+ }
+ exit(0);
+#else
+ fprintf(stderr, "fork unavailable, cannot do -loop mode\n");
+ exit(1);
+#endif
+ }
+}
+
int main(int argc, char* argv[]) {
int i, len, tmpi;
@@ -32892,6 +32977,9 @@ int main(int argc, char* argv[]) {
/* used to pass args we do not know about to rfbGetScreen(): */
int argc_vnc = 1; char *argv_vnc[128];
+ /* check for -loop mode: */
+ check_loop_mode(argc, argv);
+
dtime0(&x11vnc_start);
if (!getuid() || !geteuid()) {
@@ -33018,6 +33106,8 @@ int main(int argc, char* argv[]) {
got_connect_once = 1;
} else if (!strcmp(arg, "-many") || !strcmp(arg, "-forever")) {
connect_once = 0;
+ } else if (strstr(arg, "-loop") == arg) {
+ ; /* handled above */
} else if (!strcmp(arg, "-timeout")) {
CHECK_ARGC
first_conn_timeout = atoi(argv[++i]);
@@ -33552,6 +33642,24 @@ int main(int argc, char* argv[]) {
}
}
+
+ if (getenv("X11VNC_LOOP_MODE")) {
+ if (bg) {
+ if (! quiet) {
+ fprintf(stderr, "disabling -bg in -loop "
+ "mode\n");
+ }
+ bg = 0;
+ }
+ if (inetd) {
+ if (! quiet) {
+ fprintf(stderr, "disabling -inetd in -loop "
+ "mode\n");
+ }
+ inetd = 0;
+ }
+ }
+
if (launch_gui && (query_cmd || remote_cmd)) {
launch_gui = 0;
gui_str = NULL;