blob: 2ff93e2c90b047ec4f2c549c154060f4ca56c22e [file] [log] [blame]
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +00001.TH vncviewer 1 "05 May 2004" "TightVNC" "Virtual Network Computing"
2.SH NAME
3vncviewer \- VNC viewer for X
4.SH SYNOPSIS
5.B vncviewer
6.RI [ options ]
7.RI [ host ][: display# ]
8.br
9.B vncviewer
10.RI [ options ]
11.B \-listen
12.RI [ port ]
13.SH DESCRIPTION
14.B vncviewer
15is a viewer (client) for Virtual Network Computing. This manual page documents
16version 4 for the X window system.
17
18If you run the viewer with no arguments it will prompt you for a VNC server to
19connect to. Alternatively, specify the VNC server as an argument, e.g.:
20
21.RS
22vncviewer snoopy:2
23.RE
24
25where 'snoopy' is the name of the machine, and '2' is the display number of the
26VNC server on that machine. Either the machine name or display number can be
27omitted. So for example ":1" means display number 1 on the same machine, and
28"snoopy" means "snoopy:0" i.e. display 0 on machine "snoopy".
29
30If the VNC server is successfully contacted, you will be prompted for a
31password to authenticate you. If the password is correct, a window will appear
32showing the desktop of the VNC server.
33
34.SH AUTOMATIC PROTOCOL SELECTION
35
36The viewer tests the speed of the connection to the server and chooses the
37encoding and pixel format (color level) appropriately. This makes it much
38easier to use than previous versions where the user had to specify arcane
39command line arguments.
40
41The viewer normally starts out assuming the link is slow, using the
42encoding with the best compression. If it turns out that the link is
43fast enough it switches to an encoding which compresses less but is
44faster to generate, thus improving the interactive feel.
45
46The viewer normally starts in full-color mode, but switches to
47low-color mode if the bandwidth is insufficient. However, this only
48occurs when communicating with servers supporting protocol 3.8 or
49newer, since many old servers does not support color mode changes
50safely.
51
52Automatic selection can be turned off by setting the
53\fBAutoSelect\fP parameter to false, or from the options dialog.
54
55.SH POPUP MENU
56The viewer has a popup menu containing entries which perform various actions.
57It is usually brought up by pressing F8, but this can be configured with the
58MenuKey parameter. Actions which the popup menu can perform include:
59.RS 2
60.IP * 2
61switching in and out of full-screen mode
62.IP *
63quitting the viewer
64.IP *
65generating key events, e.g. sending ctrl-alt-del
66.IP *
67accessing the options dialog and various other dialogs
68.RE
69.PP
70By default, key presses in the popup menu get sent to the VNC server and
71dismiss the popup. So to get an F8 through to the VNC server simply press it
72twice.
73
74.SH FULL SCREEN MODE
75A full-screen mode is supported. This is particularly useful when connecting
76to a remote screen which is the same size as your local one. If the remote
77screen is bigger, you can scroll by bumping the mouse against the edge of the
78screen.
79
80Unfortunately this mode doesn't work completely with all window managers, since
81it breaks the X window management conventions.
82
83.SH OPTIONS (PARAMETERS)
84You can get a list of parameters by giving \fB\-h\fP as a command-line option
85to vncviewer. Parameters can be turned on with -\fIparam\fP or off with
86-\fIparam\fP=0. Parameters which take a value can be specified as
87-\fIparam\fP \fIvalue\fP. Other valid forms are \fIparam\fP\fB=\fP\fIvalue\fP
88-\fIparam\fP=\fIvalue\fP --\fIparam\fP=\fIvalue\fP. Parameter names are
89case-insensitive.
90
91Many of the parameters can also be set graphically via the options dialog box.
92This can be accessed from the popup menu or from the "Connection details"
93dialog box.
94
95.TP
96.B \-display \fIXdisplay\fP
97Specifies the X display on which the VNC viewer window should appear.
98
99.TP
100.B \-geometry \fIgeometry\fP
101Standard X position and sizing specification.
102
103.TP
104.B \-listen \fI[port]\fP
105Causes vncviewer to listen on the given port (default 5500) for reverse
106connections from a VNC server. WinVNC supports reverse connections initiated
107using the 'Add New Client' menu option or the '\-connect' command-line option.
108Xvnc supports reverse connections with a helper program called
109.B vncconfig.
110
111.TP
112.B \-passwd \fIpassword-file\fP
113If you are on a filesystem which gives you access to the password file used by
114the server, you can specify it here to avoid typing it in. It will usually be
115"~/.vnc/passwd".
116
117.TP
118.B \-Shared
119When you make a connection to a VNC server, all other existing connections are
120normally closed. This option requests that they be left open, allowing you to
121share the desktop with someone already using it.
122
123.TP
124.B \-ViewOnly
125Specifies that no keyboard or mouse events should be sent to the server.
126Useful if you want to view a desktop without interfering; often needs to be
127combined with
128.B \-Shared.
129
130.TP
131.B \-FullScreen
132Start in full-screen mode.
133
134.TP
135.B \-AutoSelect
136Use automatic selection of encoding and pixel format (default is on). Normally
137the viewer tests the speed of the connection to the server and chooses the
138encoding and pixel format appropriately. Turn it off with \fB-AutoSelect=0\fP.
139
140.TP
141.B \-FullColor, \-FullColour
142Tells the VNC server to send full-color pixels in the best format for this
143display. This is default.
144
145.TP
146.B \-LowColorLevel, \-LowColourLevel \fIlevel\fP
147Selects the reduced color level to use on slow links. \fIlevel\fP can range
148from 0 to 2, 0 meaning 8 colors, 1 meaning 64 colors (the default), 2 meaning
149256 colors.
150
151.TP
152.B \-PreferredEncoding \fIencoding\fP
153This option specifies the preferred encoding to use from one of "Tight", "ZRLE",
154"hextile" or "raw".
155
156.TP
157.B -UseLocalCursor
158Render the mouse cursor locally if the server supports it (default is on).
159This can make the interactive performance feel much better over slow links.
160
161.TP
162.B \-WMDecorationWidth \fIw\fP, \-WMDecorationHeight \fIh\fP
163The total width and height taken up by window manager decorations. This is
164used to calculate the maximum size of the VNC viewer window. Default is
165width 6, height 24.
166
167.TP
168.B \-log \fIlogname\fP:\fIdest\fP:\fIlevel\fP
169Configures the debug log settings. \fIdest\fP can currently be \fBstderr\fP or
170\fBstdout\fP, and \fIlevel\fP is between 0 and 100, 100 meaning most verbose
171output. \fIlogname\fP is usually \fB*\fP meaning all, but you can target a
172specific source file if you know the name of its "LogWriter". Default is
173\fB*:stderr:30\fP.
174
175.TP
176.B \-MenuKey \fIkeysym-name\fP
177This option specifies the key which brings up the popup menu. The key is
178specified as an X11 keysym name (these can be obtained by removing the XK_
179prefix from the entries in "/usr/include/X11/keysymdef.h"). Default is F8.
180
181.TP
182\fB\-via\fR \fIgateway\fR
183Automatically create encrypted TCP tunnel to the \fIgateway\fR machine
184before connection, connect to the \fIhost\fR through that tunnel
185(TightVNC\-specific). By default, this option invokes SSH local port
186forwarding, assuming that SSH client binary can be accessed as
187/usr/bin/ssh. Note that when using the \fB\-via\fR option, the host
188machine name should be specified as known to the gateway machine, e.g.
189"localhost" denotes the \fIgateway\fR, not the machine where vncviewer
190was launched. The environment variable \fIVNC_VIA_CMD\fR can override
191the default tunnel command of
192\fB/usr/bin/ssh\ -f\ -L\ "$L":"$H":"$R"\ "$G"\ sleep\ 20\fR. The tunnel
193command is executed with the environment variables \fIL\fR, \fIH\fR,
194\fIR\fR, and \fIG\fR taken the values of the local port number, the remote
195host, the port number on the remote host, and the gateway machine
196respectively.
197
198.SH SEE ALSO
199.BR Xvnc (1),
200.BR vncpasswd (1),
201.BR vncconfig (1),
202.BR vncserver (1)
203.br
204http://www.tightvnc.com
205
206.SH AUTHOR
207Tristan Richardson, RealVNC Ltd.
208
209VNC was originally developed by the RealVNC team while at Olivetti
Constantin Kaplinskybe1bda82006-06-02 04:43:52 +0000210Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +0000211implemented by Constantin Kaplinsky. Many other people participated in
212development, testing and support.