You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

vncviewer.man 6.8KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190
  1. .TH vncviewer 1 "30 December 2004" "TightVNC" "Virtual Network Computing"
  2. .SH NAME
  3. vncviewer \- 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
  15. is a viewer (client) for Virtual Network Computing. This manual page documents
  16. version 4 for the X window system.
  17. If you run the viewer with no arguments it will prompt you for a VNC server to
  18. connect to. Alternatively, specify the VNC server as an argument, e.g.:
  19. .RS
  20. vncviewer snoopy:2
  21. .RE
  22. where 'snoopy' is the name of the machine, and '2' is the display number of the
  23. VNC server on that machine. Either the machine name or display number can be
  24. omitted. So for example ":1" means display number 1 on the same machine, and
  25. "snoopy" means "snoopy:0" i.e. display 0 on machine "snoopy".
  26. If the VNC server is successfully contacted, you will be prompted for a
  27. password to authenticate you. If the password is correct, a window will appear
  28. showing the desktop of the VNC server.
  29. .SH AUTOMATIC PROTOCOL SELECTION
  30. The viewer tests the speed of the connection to the server and chooses the
  31. encoding and pixel format (color level) appropriately. This makes it much
  32. easier to use than previous versions where the user had to specify arcane
  33. command line arguments.
  34. The viewer normally starts out assuming the link is slow, using a low color
  35. level and using the encoding with the best compression. If it turns out that
  36. the link is fast enough it switches to full-color mode and will use an
  37. encoding which compresses less but is faster to generate, thus improving the
  38. interactive feel. Automatic selection can be turned off by setting the
  39. \fBAutoSelect\fP parameter to false, or from the options dialog.
  40. .SH POPUP MENU
  41. The viewer has a popup menu containing entries which perform various actions.
  42. It is usually brought up by pressing F8, but this can be configured with the
  43. MenuKey parameter. Actions which the popup menu can perform include:
  44. .RS 2
  45. .IP * 2
  46. switching in and out of full-screen mode
  47. .IP *
  48. quitting the viewer
  49. .IP *
  50. generating key events, e.g. sending ctrl-alt-del
  51. .IP *
  52. accessing the options dialog and various other dialogs
  53. .RE
  54. .PP
  55. By default, key presses in the popup menu get sent to the VNC server and
  56. dismiss the popup. So to get an F8 through to the VNC server simply press it
  57. twice.
  58. .SH FULL SCREEN MODE
  59. A full-screen mode is supported. This is particularly useful when connecting
  60. to a remote screen which is the same size as your local one. If the remote
  61. screen is bigger, you can scroll by bumping the mouse against the edge of the
  62. screen.
  63. Unfortunately this mode doesn't work completely with all window managers, since
  64. it breaks the X window management conventions.
  65. .SH OPTIONS (PARAMETERS)
  66. You can get a list of parameters by giving \fB\-h\fP as a command-line option
  67. to vncviewer. Parameters can be turned on with -\fIparam\fP or off with
  68. -\fIparam\fP=0. Parameters which take a value can be specified as
  69. -\fIparam\fP \fIvalue\fP. Other valid forms are \fIparam\fP\fB=\fP\fIvalue\fP
  70. -\fIparam\fP=\fIvalue\fP --\fIparam\fP=\fIvalue\fP. Parameter names are
  71. case-insensitive.
  72. Many of the parameters can also be set graphically via the options dialog box.
  73. This can be accessed from the popup menu or from the "Connection details"
  74. dialog box.
  75. .TP
  76. .B \-display \fIXdisplay\fP
  77. Specifies the X display on which the VNC viewer window should appear.
  78. .TP
  79. .B \-geometry \fIgeometry\fP
  80. Standard X position and sizing specification.
  81. .TP
  82. .B \-listen \fI[port]\fP
  83. Causes vncviewer to listen on the given port (default 5500) for reverse
  84. connections from a VNC server. WinVNC supports reverse connections initiated
  85. using the 'Add New Client' menu option or the '\-connect' command-line option.
  86. Xvnc supports reverse connections with a helper program called
  87. .B vncconfig.
  88. .TP
  89. .B \-passwd \fIpassword-file\fP
  90. If you are on a filesystem which gives you access to the password file used by
  91. the server, you can specify it here to avoid typing it in. It will usually be
  92. "~/.vnc/passwd".
  93. .TP
  94. .B \-Shared
  95. When you make a connection to a VNC server, all other existing connections are
  96. normally closed. This option requests that they be left open, allowing you to
  97. share the desktop with someone already using it.
  98. .TP
  99. .B \-ViewOnly
  100. Specifies that no keyboard or mouse events should be sent to the server.
  101. Useful if you want to view a desktop without interfering; often needs to be
  102. combined with
  103. .B \-Shared.
  104. .TP
  105. .B \-FullScreen
  106. Start in full-screen mode.
  107. .TP
  108. .B \-AutoSelect
  109. Use automatic selection of encoding and pixel format (default is on). Normally
  110. the viewer tests the speed of the connection to the server and chooses the
  111. encoding and pixel format appropriately. Turn it off with \fB-AutoSelect=0\fP.
  112. .TP
  113. .B \-FullColor, \-FullColour
  114. Tells the VNC server to send full-color pixels in the best format for this
  115. display. By default a low color mode is used until AutoSelect decides the
  116. link is fast enough. However if the server's native pixel format is
  117. colormapped (as opposed to truecolor) then the server's format is used by
  118. default.
  119. .TP
  120. .B \-LowColorLevel, \-LowColourLevel \fIlevel\fP
  121. Selects the reduced color level to use on slow links. \fIlevel\fP can range
  122. from 0 to 2, 0 meaning 8 colors, 1 meaning 64 colors (the default), 2 meaning
  123. 256 colors.
  124. .TP
  125. .B \-PreferredEncoding \fIencoding\fP
  126. This option specifies the preferred encoding to use from one of "ZRLE",
  127. "hextile" or "raw".
  128. .TP
  129. .B -UseLocalCursor
  130. Render the mouse cursor locally if the server supports it (default is on).
  131. This can make the interactive performance feel much better over slow links.
  132. .TP
  133. .B \-WMDecorationWidth \fIw\fP, \-WMDecorationHeight \fIh\fP
  134. The total width and height taken up by window manager decorations. This is
  135. used to calculate the maximum size of the VNC viewer window. Default is
  136. width 6, height 24.
  137. .TP
  138. .B \-log \fIlogname\fP:\fIdest\fP:\fIlevel\fP
  139. Configures the debug log settings. \fIdest\fP can currently be \fBstderr\fP or
  140. \fBstdout\fP, and \fIlevel\fP is between 0 and 100, 100 meaning most verbose
  141. output. \fIlogname\fP is usually \fB*\fP meaning all, but you can target a
  142. specific source file if you know the name of its "LogWriter". Default is
  143. \fB*:stderr:30\fP.
  144. .TP
  145. .B \-MenuKey \fIkeysym-name\fP
  146. This option specifies the key which brings up the popup menu. The key is
  147. specified as an X11 keysym name (these can be obtained by removing the XK_
  148. prefix from the entries in "/usr/include/X11/keysymdef.h"). Default is F8.
  149. .SH SEE ALSO
  150. .BR Xvnc (1)
  151. .BR vncconfig (1),
  152. .BR vncserver (1),
  153. .br
  154. http://www.tightvnc.com
  155. .SH AUTHOR
  156. Tristan Richardson, RealVNC Ltd.
  157. VNC was originally developed by the RealVNC team while at Olivetti
  158. Research Ltd / AT&T Laboratories Cambridge. TightVNC additions was
  159. implemented by Constantin Kaplinsky. Many other people participated in
  160. development, testing and support.