DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 1 | .TH vncserver 1 "26 Mar 2009" "TigerVNC" "Virtual Network Computing" |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 2 | .SH NAME |
| 3 | vncserver \- 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 ] |
DRC | eed5d1f | 2009-03-26 19:16:19 +0000 | [diff] [blame] | 15 | .RB [ \-fp |
| 16 | .IR font-path ] |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 17 | .RI [ Xvnc-options... ] |
| 18 | .br |
| 19 | .BI "vncserver \-kill :" display# |
| 20 | .SH DESCRIPTION |
| 21 | .B vncserver |
| 22 | is used to start a VNC (Virtual Network Computing) desktop. |
| 23 | .B vncserver |
| 24 | is a Perl script which simplifies the process of starting an Xvnc server. It |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 25 | runs Xvnc with appropriate options and starts a window manager on the VNC |
| 26 | desktop. |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 27 | |
| 28 | .B vncserver |
| 29 | can be run with no options at all. In this case it will choose the first |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 30 | available display number (usually :1), start Xvnc with that display number, |
| 31 | and start the default window manager in the Xvnc session. You can also |
| 32 | specify the display number, in which case vncserver will attempt to start |
| 33 | Xvnc with that display number and exit if the display number is not |
| 34 | available. For example: |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 35 | |
| 36 | .RS |
| 37 | vncserver :13 |
| 38 | .RE |
| 39 | |
| 40 | Editing the file $HOME/.vnc/xstartup allows you to change the applications run |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 41 | at startup (but note that this will not affect an existing VNC session.) |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 42 | |
| 43 | .SH OPTIONS |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 44 | You can get a list of options by passing \fB\-h\fP as an option to vncserver. |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 45 | In addition to the options listed below, any unrecognised options will be |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 46 | passed to Xvnc - see the Xvnc man page, or "Xvnc \-help", for details. |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 47 | |
| 48 | .TP |
| 49 | .B \-name \fIdesktop-name\fP |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 50 | Each VNC desktop has a name which may be displayed by the viewer. The desktop |
| 51 | name defaults to "\fIhost\fP:\fIdisplay#\fP (\fIusername\fP)", but you can |
| 52 | change it with this option. The desktop name option is passed to the xstartup |
| 53 | script via the $VNCDESKTOP environment variable, which allows you to run a |
| 54 | different set of applications depending on the name of the desktop. |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 55 | |
| 56 | .TP |
| 57 | .B \-geometry \fIwidth\fPx\fIheight\fP |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 58 | Specify the size of the VNC desktop to be created. Default is 1024x768. |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 59 | |
| 60 | .TP |
| 61 | .B \-depth \fIdepth\fP |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 62 | Specify the pixel depth (in bits) of the VNC desktop to be created. Default is |
| 63 | 24. Other possible values are 8, 15 and 16 - anything else is likely to cause |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 64 | strange behaviour by applications. |
| 65 | |
| 66 | .TP |
| 67 | .B \-pixelformat \fIformat\fP |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 68 | Specify pixel format for Xvnc to use (BGRnnn or RGBnnn). The default for |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 69 | depth 8 is BGR233 (meaning the most significant two bits represent blue, the |
| 70 | next three green, and the least significant three represent red), the default |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 71 | for depth 16 is RGB565, and the default for depth 24 is RGB888. |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 72 | |
| 73 | .TP |
| 74 | .B \-cc 3 |
| 75 | As an alternative to the default TrueColor visual, this allows you to run an |
| 76 | Xvnc server with a PseudoColor visual (i.e. one which uses a color map or |
| 77 | palette), which can be useful for running some old X applications which only |
| 78 | work on such a display. Values other than 3 (PseudoColor) and 4 (TrueColor) |
| 79 | for the \-cc option may result in strange behaviour, and PseudoColor desktops |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 80 | must have an 8-bit depth. |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 81 | |
| 82 | .TP |
| 83 | .B \-kill :\fIdisplay#\fP |
| 84 | This kills a VNC desktop previously started with vncserver. It does this by |
| 85 | killing the Xvnc process, whose process ID is stored in the file |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 86 | "$HOME/.vnc/\fIhost\fP:\fIdisplay#\fP.pid". The |
| 87 | .B \-kill |
| 88 | option ignores anything preceding the first colon (":") in the display |
| 89 | argument. Thus, you can invoke "vncserver \-kill $DISPLAY", for example at the |
| 90 | end of your xstartup file after a particular application exits. |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 91 | |
DRC | eed5d1f | 2009-03-26 19:16:19 +0000 | [diff] [blame] | 92 | .TP |
| 93 | .B \-fp \fIfont-path\fP |
| 94 | The vncserver script will normally examine your system to figure out where it |
| 95 | stores its X11 fonts and then generate an appropriate font path argument for |
| 96 | Xvnc based on this. If your system stores its X11 fonts in a location that |
| 97 | vncserver does not know about, however, then this may fail. In that case, |
| 98 | vncserver will then try to contact the local X Font Server (xfs) on port 7100. |
| 99 | Not all systems have xfs installed and running, so this may fail as well. In |
| 100 | that case, you can manually specify a font path by using the |
| 101 | .B \-fp |
| 102 | argument to vncserver. |
| 103 | |
| 104 | If you prefer to use the X Font Server by default rather than a static font |
| 105 | path, then you can run |
| 106 | |
| 107 | .RS |
| 108 | .RS |
| 109 | vncserver -fp unix/:7100 |
| 110 | .RE |
| 111 | .RE |
| 112 | |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 113 | .SH FILES |
| 114 | Several VNC-related files are found in the directory $HOME/.vnc: |
| 115 | .TP |
| 116 | $HOME/.vnc/xstartup |
| 117 | A shell script specifying X applications to be run when a VNC desktop is |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 118 | started. If this file does not exist, then vncserver will create a default |
| 119 | xstartup script which attempts to launch your chosen window manager. |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 120 | .TP |
| 121 | $HOME/.vnc/passwd |
| 122 | The VNC password file. |
| 123 | .TP |
| 124 | $HOME/.vnc/\fIhost\fP:\fIdisplay#\fP.log |
| 125 | The log file for Xvnc and applications started in xstartup. |
| 126 | .TP |
| 127 | $HOME/.vnc/\fIhost\fP:\fIdisplay#\fP.pid |
| 128 | Identifies the Xvnc process ID, used by the |
| 129 | .B \-kill |
| 130 | option. |
| 131 | |
| 132 | .SH SEE ALSO |
| 133 | .BR vncviewer (1), |
| 134 | .BR vncpasswd (1), |
| 135 | .BR vncconfig (1), |
| 136 | .BR Xvnc (1) |
| 137 | .br |
Peter Åstrand | 4eacc02 | 2009-02-27 10:12:14 +0000 | [diff] [blame] | 138 | http://www.tigervnc.org |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 139 | |
| 140 | .SH AUTHOR |
| 141 | Tristan Richardson, RealVNC Ltd. |
DRC | 7fe258a | 2009-03-26 18:58:40 +0000 | [diff] [blame] | 142 | .br |
| 143 | D. R. Commander |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 144 | |
| 145 | VNC was originally developed by the RealVNC team while at Olivetti |
Constantin Kaplinsky | be1bda8 | 2006-06-02 04:43:52 +0000 | [diff] [blame] | 146 | Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 147 | implemented by Constantin Kaplinsky. Many other people participated in |
| 148 | development, testing and support. |