thanks for your reply ,
I wrote two files in /etc/xinet.d/ ,file my_vnc_nowait is nowait mode,and my_vnc_wait is the wait mode ,as following :

service my_vnc_nowait
{
       socket_type      = stream
       wait                     = no
       user             = nobody
       serve            = /usr/local/bin/Xvnc
server_args = -inetd -query 127.0.0.1 -once -geometry 1024x768
       disable  = no
}
service my_vnc_wait
{
       socket_type      = stream
       wait                     = yes
       user             = root
       server   = /usr/local/bin/Xvnc
server_args = -inetd -query 127.0.0.1 -once passwordFile=/root/.vnc/passwd -geometry 1024x768
       disable  = no
}

surprisingly , the "nowait mode" can work well .But the wait mode, when connect to the wait mode port , it told : " read:Connection reset by peer (10054) "

why ? how to make it work ?

**************************************************************
From: Wesley Hart <[EMAIL PROTECTED]>
To: ?? ? <[EMAIL PROTECTED]>, vnc-list@realvnc.com
CC: vnc-list@realvnc.com
Subject: Re: Again:make the vnc as a standard  service in linux
Date: Thu, 16 Jun 2005 10:17:28 -0500

Twas brillig, and ?? ? scrobe:
> I have read the article wrote by Jeremy Impson at
> http://linuxjournal.com/article/5499.
> He said that there are 2 ways to make the vnc a service ,but also pointed
> out  both have drawbacks :
> Some distributions like Fc3  set the vncserver boot script (in
> /etc/init.d/vncserver) to come up at boot,but this configuration doesn't
> scale well for multiple users. You could define many VNC sessions in the
> /etc/sysconfig/vncservers file to start up at boot. But all of these VNC
> desktops will be idle until they are used. all of these take up RAM.
> with the xinetd method ,  the VNC server  start a new desktop for every
> connection, disallows multiple connections to one desktop and shuts down
> after the original connection exits. So it loses statefulness and the
> ability to share the desktop both remotely and locally.

That article may be a bit out of date.  Take a look at the Xvnc man page
section on 'USAGE WITH INETD'

  http://www.realvnc.com/products/free/4.1/man/Xvnc.html

You want to run Xvnc with inetd's "wait" option.  I'm using this locally
and it seems to address all of your concerns about multiple connections,
session persistance and desktop sharing.  Check it out.

--
Wesley Hart

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
_______________________________________________
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to