vinagre(1) [suse man page]
VINAGRE(1) General Commands Manual VINAGRE(1) NAME
vinagre - a remote desktop viewer for the GNOME Desktop SYNOPSYS
vinagre [OPTIONS] [server][::port|:display] DESCRIPTION
vinagre is a remote desktop viewer for the GNOME desktop. It can support many protocols using a plugin system. Current plugins exist for VNC and SSH. Vinagre has many features, among others:. - Support for multiple connections simultaneously - Bookmarks and history support - Avahi integration - GNOME keyring integration - GNOME panel applet to quickly launch vinagre to access VNC servers - You can connect to a VNC server by double clicking on a .vnc file when using nautilus. OPTIONS
Help Options: -?, --help Show help options --help-all Show all help options --help-gtk Show GTK+ options Application Options: --help-vnc Show VNC options -F, --file=filename Opens a .vnc file -f, --fullscreen Open vinagre in fullscreen mode -n, --new-window Create a new toplevel window in an existing instance of vinagre --display=DISPLAY X display to use Run 'vinagre --help' to see a full list of available command line options OPERANDS
The following operands are supported: [server][::port|:display] Specifies the VNC server to connect to. The VNC server can be either a hostname, or an IP address. If the server is an IPv6 address, it must be enclosed by square brackets. The address can optionally be followed by two colons (::) and the VNC port number, or alter- natively by one colon (:) and the display where Vinagre should run. If a port is not specified, default value of 5900 will be used. If the value is lower than 1024, 5900 will be added to it. For example, ":0" means "5900" and ":1" means ":5901". If only a port is specified, but not the hostname, localhost will be assumed. Possible values for the display are between 0 and 1024. If a display number greater than 1024 is specified, it will be assumed to be a port. Note that you can't specify the port and the display at the same time. EXAMPLES
Example 1: Start vinagre from the command line example% vinagre Example 2: Create a new top-level window example% vinagre --new-window Example 3: Connect to a specified VNC server and port example% vinagre snoopy::5900 Example 4: Connect to a specified IPv4 address and port example% vinagre 192.168.1.35::2700 Example 5: Connect to a specified IPv6 address and port example% vinagre [2001:0db8:0:0:0:0:1428:57ab]::2700 Example 6: Connect to a VNC server specified by a .vnc file example% vinagre -F snoopy.vnc Example 7: Connect to localhost on a specified port in fullscreen mode example% vinagre -f ::5900 SEE ALSO
Vinagre help manual AUTHOR
Vinagre was written by Jonh Wendell <wendell@bani.com.br> This manual page was written by Emilio Pozuelo Monfort <pochu@ubuntu.com> and Halton Huo <halton.huo@sun.com>. User Commands August 12th 2009 VINAGRE(1)
Check Out this Related Man Page
vncconfig(1) Virtual Network Computing vncconfig(1) NAME
vncconfig - configure and control a VNC server SYNOPSIS
vncconfig [parameters] vncconfig [parameters] -connect host[:port] vncconfig [parameters] -disconnect vncconfig [parameters] [-set] Xvnc-param=value ... vncconfig [parameters] -list vncconfig [parameters] -get Xvnc-param vncconfig [parameters] -desc Xvnc-param DESCRIPTION
vncconfig is used to configure and control a running instance of Xvnc, or any other X server with the VNC extension. Note that it cannot be used to control VNC servers prior to version 4. When run with no options, it runs as a kind of "helper" application for Xvnc. Its main purpose when run in this mode is to support clip- board transfer to and from the VNC viewer(s). Note that without a running instance of vncconfig there will be no clipboard support. It puts up a window with some checkboxes which can be used to disable clipboard transfers if required (in the future there may be more func- tions available from this window). The -nowin flag can be used if you always want clipboard support but don't wish to clutter the desktop with this window - alternatively the -iconic option can be used to make it iconified by default. When run in any other mode, vncconfig is a one-shot program used to configure or control Xvnc as appropriate. It can be used to tell Xvnc to connect or disconnect from listening viewers, and to set and retrieve Xvnc's parameters. Note that the DISPLAY environment variable or the -display option must be set as appropriate to control Xvnc. If you run it on an ordinary X server (or on a version 3 Xvnc) you will get an error message saying that there is no VNC extension. OPTIONS
-connect host[:port] Tells an Xvnc server to make a "reverse" connection to a listening VNC viewer (normally connections are made the other way round - the viewer connects to the server). host is the host where the listening viewer is running. If it's not listening on the default port of 5500, you can specify host:port instead. -disconnect This causes Xvnc to disconnect from all viewers so that the VNC desktop is not displayed anywhere. [-set] Xvnc-param=value Sets an Xvnc parameter to the given value. Note that some of Xvnc's parameters are read only once at startup so that changing them in this way may not have any effect. -list Lists all the parameters supported by Xvnc. -get Xvnc-param Prints the current value of the given Xvnc parameter. -desc Xvnc-param Prints a short description of the given Xvnc parameter. PARAMETERS
vncconfig also has parameters of its own which can be set on the command line. These should not be confused with Xvnc's parameters which are manipulated with the -set, -get, -list and -desc options. Parameters can be turned on with -param or off with -param=0. Parameters which take a value can be specified as -param value. Other valid forms are param=value -param=value --param=value. Parameter names are case-insensitive. -display Xdisplay Specifies the Xvnc server to control. -nowin When run as a "helper" app, don't put up a window. -iconic When run as a "helper" app, make the window iconified at startup. SEE ALSO
vncpasswd(1), vncviewer(1), vncserver(1), Xvnc(1) http://www.tigervnc.org AUTHOR
Tristan Richardson, RealVNC Ltd. VNC was originally developed by the RealVNC team while at Olivetti Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people participated in development, testing and support. TigerVNC 17 Apr 2006 vncconfig(1)