Difference between revisions of "Vnc"

From Bashlinux
Jump to: navigation, search
Line 2: Line 2:
 
== VNC ==
 
== VNC ==
 
x11vnc is reliable vnc server which doesn't take much or even all the CPU usage. To install it run:
 
x11vnc is reliable vnc server which doesn't take much or even all the CPU usage. To install it run:
  +
 
 
<pre><nowiki>
 
<pre><nowiki>
# yum -y install x11vnc
+
# yum -y install x11vnc
</nowiki></pre>
+
</nowiki></pre>
   
   
Line 11: Line 11:
   
 
To improve the usage of VNC, it can be triggered by xinetd, a configuration file under `/etc/xinetd.d` must look like
 
To improve the usage of VNC, it can be triggered by xinetd, a configuration file under `/etc/xinetd.d` must look like
  +
 
 
<pre><nowiki>
 
<pre><nowiki>
service x11vnc
+
service x11vnc
{
+
{
disable = no
+
disable = no
socket_type = stream
+
socket_type = stream
protocol = tcp
+
protocol = tcp
port = 5900
+
port = 5900
wait = no
+
wait = no
user = root
+
user = root
server = /usr/bin/x11vnc
+
server = /usr/bin/x11vnc
server_args = -inetd -display :0 -scale 2/3 -ncache 10 -auth /var/gdm/\:0.Xauth -usepw -rfbauth /opt/bashlinux/.vnc/passwd -o /opt/bashlinux/.vnc/x11vnc.log
+
server_args = -inetd -display :0 -scale 2/3 -ncache 10 -auth /var/gdm/\:0.Xauth -usepw -rfbauth /opt/bashlinux/.vnc/passwd -o /opt/bashlinux/.vnc/x11vnc.log
}
+
}
   
</nowiki></pre>
+
</nowiki></pre>
   
 
That means that a service with such name must be created in order to let xinetd know which service to trigger when the desired port is bind. it could be accomplished by adding it to `/etc/services`
 
That means that a service with such name must be created in order to let xinetd know which service to trigger when the desired port is bind. it could be accomplished by adding it to `/etc/services`
  +
 
 
<pre><nowiki>
 
<pre><nowiki>
# echo "x11vnc 5900/tcp" >> /etc/services
+
# echo "x11vnc 5900/tcp" >> /etc/services
</nowiki></pre>
+
</nowiki></pre>
   
 
At the end, ensure that X server grants access to '''DISPLAY 0''' by adding at the end of the `~/.bashrc` file:
 
At the end, ensure that X server grants access to '''DISPLAY 0''' by adding at the end of the `~/.bashrc` file:
  +
 
 
<pre><nowiki>
 
<pre><nowiki>
xhost +
+
xhost +
</nowiki></pre>
+
</nowiki></pre>
   
   

Revision as of 07:26, 25 January 2011

VNC

x11vnc is reliable vnc server which doesn't take much or even all the CPU usage. To install it run:

# yum -y install x11vnc


VNC on demand

To improve the usage of VNC, it can be triggered by xinetd, a configuration file under `/etc/xinetd.d` must look like

service x11vnc
{
        disable         = no
        socket_type     = stream
        protocol        = tcp
        port            = 5900
        wait            = no
        user            = root
        server          = /usr/bin/x11vnc
        server_args     = -inetd -display :0 -scale 2/3 -ncache 10 -auth /var/gdm/\:0.Xauth -usepw -rfbauth /opt/bashlinux/.vnc/passwd -o /opt/bashlinux/.vnc/x11vnc.log
}

That means that a service with such name must be created in order to let xinetd know which service to trigger when the desired port is bind. it could be accomplished by adding it to `/etc/services`

# echo "x11vnc 5900/tcp" >> /etc/services

At the end, ensure that X server grants access to DISPLAY 0 by adding at the end of the `~/.bashrc` file:

xhost +


#!wiki important
'''Important'''
 
Please ensure that xinetd is installed before start VNC setup.


VNC on on demand over SSL

Some things that should be considered in order to get connection to a vnc terminal are:

  • Iptables is set to only listen for VNC calls from server, to get connection from your terminal you need to remove the statement `-s 10.0.0.1` on `/etc/sysconfig/iptables` rule for vnc.
  • To do vnc from mac use ssvnc, it is available at [[1]]
  • add the following option at the end of the `x11vnc` command arguments
 -ssl SAVE
 


Links

  • x11vnc certificates and key management
[[2]]