cannot kill vncserver

[Daniel Senderowicz]

Hi Robin,

I guess my confussion came from what you said about having
this service configuration for transient terminal use, that
is not what I prefer in the specific case of VNC. Again,
many thanks for your help and your explanation.

Regards,

Daniel

>On Tue Oct 28, 2008 at 07:01:44AM -0700, Daniel Senderowicz wrote:
>
>> Hi Robin,
>> 
>> I just commented out the file "vncts" in /etc/xinetd.d and
>> now works well. However I don't understand what is that file
>> supposed to do in the overall context. Thank you very much
>> for your help!
>> 
>Glad it's working now.  I'll try to explain what the problem was:
>
>inetd (and it's more modern replacement xinetd) are central daemon
>(server) processes designed to handle large numbers of infrequently-used
>and/or transient services.
>
>Each service defines a port and a command to run on connection, so when
>any client connects on the port, the command is run and the client now
>talks to the relevant server.  Once the client disconnects, the server
>exits again.
>
>This is mainly used for services like telnet, FTP, finger, echo, daytime
>(a lot of which aren't even used on most modern systems).  These don't
>need to maintain any data between connections, so can be quickly started
>to deal with a connection, then shut down again, freeing up the memory
>for other processes.
>
>An additional benefit is that inetd/xinetd allow basic connection
>filtering to be done centrally (e.g. limiting which IP addresses can
>talk to a service) without needing a special setup for each individual
>service.
>
>Anyway, the vncts service that was defined on your system is obviously
>intended for transient VNC terminal services usage - if you connect to
>one of those screens via a VNC client, you'll get a server automatically
>started and can work remotely.  Once the client exits then the server
>shuts down and all processes within it are killed.  This can be useful
>in some circumstances, allowing a number of people to share the same
>server without needing to set up specific VNC servers, but for a single
>user system it's usually preferable to run a single, persistent, VNC
>server.
>
>Anyway, you can check the xinetd manual page for further details of what
>it does and how to configure it - if you don't use any of the services
>it's providing then you might want to shut it down altogether.
>
>Cheers,
>    Robin
>-- 
>     ___        
>    ( ' }     |       Robin Hill        <robin "at" robinhill.me.uk> |
>   / / )      | Little Jim says ....                            |
>  // !!       |      "He fallen in de water !!"                 |
>_______________________________________________
>VNC-List mailing list
>VNC-List "at" realvnc.com
>To remove yourself from the list visit:
>http://www.realvnc.com/mailman/listinfo/vnc-list
>