blob: 04a060ec33595d5b3a3639215a66967c6c196834 [file] [log] [blame]
Pierre Ossmanf256a1a2014-09-17 14:09:58 +02001.TH vncserver 1 "" "TigerVNC" "Virtual Network Computing"
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +00002.SH NAME
3vncserver \- start or stop a VNC server
4.SH SYNOPSIS
5.B vncserver
6.RI [: display# ]
7.RB [ \-name
8.IR desktop-name ]
9.RB [ \-geometry
10.IR width x height ]
11.RB [ \-depth
12.IR depth ]
13.RB [ \-pixelformat
14.IR format ]
DRCeed5d1f2009-03-26 19:16:19 +000015.RB [ \-fp
16.IR font-path ]
DRC8fb11912011-03-03 10:42:14 +000017.RB [ \-fg ]
Adam Tkac38ba8cf2011-04-27 11:28:09 +000018.RB [ \-autokill ]
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000019.RI [ Xvnc-options... ]
20.br
21.BI "vncserver \-kill :" display#
Pierre Ossmanc16bb272014-09-17 14:18:31 +020022.br
23.BI "vncserver \-list"
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000024.SH DESCRIPTION
25.B vncserver
26is used to start a VNC (Virtual Network Computing) desktop.
27.B vncserver
28is a Perl script which simplifies the process of starting an Xvnc server. It
DRC7fe258a2009-03-26 18:58:40 +000029runs Xvnc with appropriate options and starts a window manager on the VNC
30desktop.
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000031
32.B vncserver
33can be run with no options at all. In this case it will choose the first
DRC7fe258a2009-03-26 18:58:40 +000034available display number (usually :1), start Xvnc with that display number,
35and start the default window manager in the Xvnc session. You can also
36specify the display number, in which case vncserver will attempt to start
37Xvnc with that display number and exit if the display number is not
38available. For example:
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000039
40.RS
41vncserver :13
42.RE
43
44Editing the file $HOME/.vnc/xstartup allows you to change the applications run
DRC7fe258a2009-03-26 18:58:40 +000045at startup (but note that this will not affect an existing VNC session.)
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000046
47.SH OPTIONS
DRC7fe258a2009-03-26 18:58:40 +000048You can get a list of options by passing \fB\-h\fP as an option to vncserver.
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000049In addition to the options listed below, any unrecognised options will be
DRC7fe258a2009-03-26 18:58:40 +000050passed to Xvnc - see the Xvnc man page, or "Xvnc \-help", for details.
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000051
52.TP
53.B \-name \fIdesktop-name\fP
DRC7fe258a2009-03-26 18:58:40 +000054Each VNC desktop has a name which may be displayed by the viewer. The desktop
55name defaults to "\fIhost\fP:\fIdisplay#\fP (\fIusername\fP)", but you can
56change it with this option. The desktop name option is passed to the xstartup
57script via the $VNCDESKTOP environment variable, which allows you to run a
58different set of applications depending on the name of the desktop.
Pierre Ossman23f67c32014-09-17 16:28:56 +020059.
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000060.TP
61.B \-geometry \fIwidth\fPx\fIheight\fP
DRC7fe258a2009-03-26 18:58:40 +000062Specify the size of the VNC desktop to be created. Default is 1024x768.
Pierre Ossman23f67c32014-09-17 16:28:56 +020063.
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000064.TP
65.B \-depth \fIdepth\fP
DRC7fe258a2009-03-26 18:58:40 +000066Specify the pixel depth (in bits) of the VNC desktop to be created. Default is
6724. Other possible values are 8, 15 and 16 - anything else is likely to cause
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000068strange behaviour by applications.
Pierre Ossman23f67c32014-09-17 16:28:56 +020069.
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000070.TP
71.B \-pixelformat \fIformat\fP
DRC7fe258a2009-03-26 18:58:40 +000072Specify pixel format for Xvnc to use (BGRnnn or RGBnnn). The default for
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000073depth 8 is BGR233 (meaning the most significant two bits represent blue, the
74next three green, and the least significant three represent red), the default
DRC7fe258a2009-03-26 18:58:40 +000075for depth 16 is RGB565, and the default for depth 24 is RGB888.
Pierre Ossman23f67c32014-09-17 16:28:56 +020076.
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000077.TP
78.B \-cc 3
79As an alternative to the default TrueColor visual, this allows you to run an
80Xvnc server with a PseudoColor visual (i.e. one which uses a color map or
81palette), which can be useful for running some old X applications which only
82work on such a display. Values other than 3 (PseudoColor) and 4 (TrueColor)
83for the \-cc option may result in strange behaviour, and PseudoColor desktops
DRC7fe258a2009-03-26 18:58:40 +000084must have an 8-bit depth.
Pierre Ossman23f67c32014-09-17 16:28:56 +020085.
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +000086.TP
87.B \-kill :\fIdisplay#\fP
88This kills a VNC desktop previously started with vncserver. It does this by
89killing the Xvnc process, whose process ID is stored in the file
DRC7fe258a2009-03-26 18:58:40 +000090"$HOME/.vnc/\fIhost\fP:\fIdisplay#\fP.pid". The
91.B \-kill
92option ignores anything preceding the first colon (":") in the display
93argument. Thus, you can invoke "vncserver \-kill $DISPLAY", for example at the
94end of your xstartup file after a particular application exits.
Pierre Ossman23f67c32014-09-17 16:28:56 +020095.
DRCeed5d1f2009-03-26 19:16:19 +000096.TP
97.B \-fp \fIfont-path\fP
DRC36546c12009-04-15 06:47:23 +000098If the vncserver script detects that the X Font Server (XFS) is running, it
99will attempt to start Xvnc and configure Xvnc to use XFS for font handling.
100Otherwise, if XFS is not running, the vncserver script will attempt to start
101Xvnc and allow Xvnc to use its own preferred method of font handling (which may
102be a hard-coded font path or, on more recent systems, a font catalog.) In
103any case, if Xvnc fails to start, the vncserver script will then attempt to
104determine an appropriate X font path for this system and start Xvnc using
105that font path.
106
107The
DRCeed5d1f2009-03-26 19:16:19 +0000108.B \-fp
DRC36546c12009-04-15 06:47:23 +0000109argument allows you to override the above fallback logic and specify a font
110path for Xvnc to use.
Pierre Ossman23f67c32014-09-17 16:28:56 +0200111.
DRC8fb11912011-03-03 10:42:14 +0000112.TP
113.B \-fg
Adam Tkacf586b842011-04-27 11:20:18 +0000114Runs Xvnc as a foreground process. This has two effects: (1) The VNC server
115can be aborted with CTRL-C, and (2) the VNC server will exit as soon as the
116user logs out of the window manager in the VNC session. This may be necessary
117when launching TigerVNC from within certain grid computing environments.
Pierre Ossman23f67c32014-09-17 16:28:56 +0200118.
Adam Tkac38ba8cf2011-04-27 11:28:09 +0000119.TP
120.B \-autokill
121Automatically kill Xvnc whenever the xstartup script exits. In most cases,
122this has the effect of terminating Xvnc when the user logs out of the window
123manager.
Pierre Ossman23f67c32014-09-17 16:28:56 +0200124.
Pierre Ossmanc16bb272014-09-17 14:18:31 +0200125.TP
126.B \-list
127Lists all VNC desktops started by vncserver.
128
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +0000129.SH FILES
130Several VNC-related files are found in the directory $HOME/.vnc:
131.TP
132$HOME/.vnc/xstartup
133A shell script specifying X applications to be run when a VNC desktop is
DRC7fe258a2009-03-26 18:58:40 +0000134started. If this file does not exist, then vncserver will create a default
135xstartup script which attempts to launch your chosen window manager.
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +0000136.TP
137$HOME/.vnc/passwd
138The VNC password file.
139.TP
140$HOME/.vnc/\fIhost\fP:\fIdisplay#\fP.log
141The log file for Xvnc and applications started in xstartup.
142.TP
143$HOME/.vnc/\fIhost\fP:\fIdisplay#\fP.pid
144Identifies the Xvnc process ID, used by the
145.B \-kill
146option.
147
148.SH SEE ALSO
149.BR vncviewer (1),
150.BR vncpasswd (1),
151.BR vncconfig (1),
152.BR Xvnc (1)
153.br
Peter Åstrand4eacc022009-02-27 10:12:14 +0000154http://www.tigervnc.org
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +0000155
156.SH AUTHOR
Pierre Ossmane37a1442014-09-17 14:08:16 +0200157Tristan Richardson, RealVNC Ltd., D. R. Commander and others.
Constantin Kaplinskyb30ae7f2006-05-25 05:04:46 +0000158
159VNC was originally developed by the RealVNC team while at Olivetti
Constantin Kaplinskybe1bda82006-06-02 04:43:52 +0000160Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were
Pierre Ossmane37a1442014-09-17 14:08:16 +0200161implemented by Constantin Kaplinsky. Many other people have since
162participated in development, testing and support. This manual is part
163of the TigerVNC software suite.