blob: 33f7d4910745d1b091ab747cb083e179b1a58290 [file] [log] [blame]
Peter Åstrand9fb4e0e2004-12-30 10:03:00 +00001.TH vncconfig 1 "30 December 2004" "TightVNC" "Virtual Network Computing"
Constantin Kaplinsky47ed8d32004-10-08 09:43:57 +00002.SH NAME
3vncconfig \- configure and control a VNC server
4.SH SYNOPSIS
5.B vncconfig
6[\fB\-display\fP \fIXdisplay\fP] [\fB\-nowin\fP] [\fB\-iconic\fP]
7.br
8.B vncconfig
9[\fB\-display\fP \fIXdisplay\fP]
10.B \-connect
11.IR host [: port ]
12.br
13.B vncconfig
14[\fB\-display\fP \fIXdisplay\fP]
15.B \-disconnect
16.br
17.B vncconfig
18[\fB\-display\fP \fIXdisplay\fP]
19.IR param = value " ..."
20.br
21.B vncconfig
22[\fB\-display\fP \fIXdisplay\fP]
23.B \-list
24.br
25.B vncconfig
26[\fB\-display\fP \fIXdisplay\fP]
27\fB\-get\fP \fIparam\fP
28.br
29.B vncconfig
30[\fB\-display\fP \fIXdisplay\fP]
31\fB\-desc\fP \fIparam\fP
32.SH DESCRIPTION
33.B vncconfig
34is used to configure and control a running instance of Xvnc, or any other X
35server with the VNC extension. Note that it cannot be used to control VNC
36servers prior to version 4.
37
38When run with no options, it runs as a kind of "helper" application for Xvnc.
39Its main purpose when run in this mode is to support clipboard transfer to and
40from the VNC viewer(s). Note that without a running instance of
41\fBvncconfig\fP there will be no clipboard support. It puts up a window with
42some checkboxes which can be used to disable clipboard transfers if required
43(in the future there may be more functions available from this window). The
44\fB-nowin\fP flag can be used if you always want clipboard support but don't
45wish to clutter the desktop with this window - alternatively the \fB-iconic\fP
46option can be used to make it iconified by default.
47
48When run in any other mode, \fBvncconfig\fP is a one-shot program used to
49configure or control Xvnc as appropriate. It can be used to tell Xvnc to
50connect or disconnect from listening viewers, and to set and retrieve Xvnc's
51parameters.
52
53Note that the DISPLAY environment variable or the \fB\-display\fP option
54must be set as appropriate to control Xvnc. If you run it on an ordinary X
55server (or on a version 3 Xvnc) you will get an error message saying that there
56is no VNC extension.
57
58.SH OPTIONS
59.TP
60.B \-display \fIXdisplay\fP
61Specifies the Xvnc server to control.
62
63.TP
64.B \-nowin
65When run as a "helper" app, don't put up a window.
66
67.TP
68.B \-iconic
69When run as a "helper" app, make the window iconified at startup.
70
71.TP
72.B \-connect \fIhost\fP[:\fIport\fP]
73Tells an Xvnc server to make a "reverse" connection to a listening VNC viewer
74(normally connections are made the other way round - the viewer connects to the
75server). \fIhost\fP is the host where the listening viewer is running. If it's
76not listening on the default port of 5500, you can specify \fIhost:port\fP
77instead.
78
79.TP
80.B \-disconnect
81This causes Xvnc to disconnect from all viewers so that the VNC desktop is not
82displayed anywhere.
83
84.TP
85.IR param = value
86Sets an Xvnc parameter to the given value. Note that some of Xvnc's parameters
87are read only once at startup so that changing them in this way may not have
88any effect.
89
90.TP
91.B \-list
92Lists all the parameters supported by Xvnc.
93
94.TP
95.B \-get \fIparam\fP
96Prints the current value of the given Xvnc parameter.
97
98.TP
99.B \-desc \fIparam\fP
100Prints a short description of the given Xvnc parameter.
101
102.SH SEE ALSO
103.BR vncpasswd (1),
104.BR vncviewer (1),
105.BR vncserver (1),
106.BR Xvnc (1)
107.br
Peter Åstrand9fb4e0e2004-12-30 10:03:00 +0000108http://www.tightvnc.com
Constantin Kaplinsky47ed8d32004-10-08 09:43:57 +0000109
110.SH AUTHOR
111Tristan Richardson, RealVNC Ltd.
112
Peter Åstrand9fb4e0e2004-12-30 10:03:00 +0000113VNC was originally developed by the RealVNC team while at Olivetti
114Research Ltd / AT&T Laboratories Cambridge. TightVNC additions was
115implemented by Constantin Kaplinsky. Many other people participated in
116development, testing and support.