* Start Up VNC Server
* Start Up VNC Server [#e871813a]
Basically, this step is just the same as xf4vnc.

** Using the standalone (Xvnc) version
** Using the standalone (Xvnc) version [#cfe6cd47]

If you prefer to use Xvnc, just run vncserver script as traditional vnc servers. 

 % vncserver

*** Specifying the FontPath
*** Install X fonts [#ke6637a9]

Xvnc server requires misc and 75dpi fonts.

In the case of Fedora 10:
 % yum install xorg-x11-fonts-75dpi xorg-x11-fonts-misc

*** Specifying the FontPath [#y96a8617]

If X font server is running in your system, the following instruction is not needed.

If X font server is not running in your system, you need to specify the FontPath by the command line option or customize vncserver script to your system.

For example,

 % vncserver -fp /usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/fonts/75dpi

*** Changing the window manager
*** Changing the window manager [#fda21d1e]

By default, twm will be launched.
Customize the ~/.vnc/xstartup as you like.

E.g., On Fedora, use the following script.

 #!/bin/sh
 unset SESSION_MANAGER
 exec /etc/X11/xinit/xinitrc

If /etc/X11/xinit/xinitrc is not exist, specify one of the followings;

- GNOME
 gnome-session

- KDE
 startkde

- Xfce4
 startxfce4

- CDE
 dtsession

*** Customize 
*** Customize [#y06265ff]

To change the policy of detecting transparent window, specify the following option

 -tpwin [auto|root|wmon]

 auto ... automatically detects transparent window (default)
 root ... make root window transparent (just like rootless X server)
 wmon ... wait until the window monitor is connected (after the window monitor is connected, behave just same as 'auto')

** Using the :0 (vnc.so) version
** Using the :0 (vnc.so) version [#lc9c215e]

If you wan to share your linux desktop, you need to edit the /etc/X11/XF86Config (for XFree86) or /etc/X11/xorg.conf (for X.org). Example of this file is included as xorg.conf.vnc.

The following steps are necessary to modify your /etc/X11/XF86Config or /etc/X11/xorg.conf.

+ Add the followings to the "ServerLayout" section.
~
         InputDevice    "vncMouse" "ExtraPointer"
         InputDevice    "vncKeyboard" "ExtraKeyboard"
~
+ Add the followings to the "Module" section.
~
         Load  "vnc"
~
+ Add the following sections.
~
 Section "InputDevice"
         Identifier  "vncMouse"
         Driver      "rfbmouse"
 EndSection
 
 Section "InputDevice"
         Identifier  "vncKeyboard"
         Driver      "rfbkeyb"
 EndSection
~
+ Add the followings to the "Device" section.
~
         Option      "usevnc" "on"
         Option      "useraccept" "off"

*** Customize 
*** Customize [#g19ae363]

To change the policy of detecting transparent window, Add the followings to the "Device" section.

         Option      "tpwin" ["auto"|"root"|"wmon"]

 auto ... automatically detects transparent window (default)
 root ... make root window transparent (just like rootless X server)
 wmon ... wait until the window monitor is connected (after the window monitor is connected, behave just same as 'auto')

* Start Up windowmonitor
* Start Up windowmonitor [#zcd6dc7f]
The windowmonitor is required to support clipboard and the Meta window manager features.

The windowmonitor is implemented as a kind of vnc client. Usually you need an authentication process. By specifying a vncpassword file using a '-passwd' option, keyboard interaction can be omitted.

IMPORTANT: You have to run the windowmonitor as a X client of the X server provided by the metavnc server.

Using the autostart feature of GNOME or KDE is a nice way to start the windowmonitor.

The following is an example how to auto-start the windowmonitor on GNOME;

+ Launch "Preferences" - "More Preferences" - "Sessions" from the start menu.
+ Click the "Startup Programs" tab and add the command.
+ The startup command should be "/usr/bin/windowmonitor -passwd ~/.vnc/passwd", or whatsoever.

The following is an example how to auto-start the windowmonitor on KDE;

+ Create a startup script to launch the window monitor. For example,
 /usr/bin/windowmonitor -passwd ~/.vnc/passwd
+ Put the script in ~/.kde/AutoStart/.

* Using the RealVNC4's vncconfig
* Using the RealVNC4's vncconfig [#j6cfe1af]
Another option to support clipboard is to use the RealVNC4's vncconfig.
The good point of the vncconfig is that it uses the X Extensions and does not need any authentication like the windowmonitor.

The vncconfig is not included in the metavnc packages.

Front page   Edit Diff Backup Upload Copy Rename Reload   New List of pages Search Recent changes   Help   RSS of recent changes