I have not done a lot of TCP socket programming and my "view of this world" is probably overly simplistic, but I thought that if the vnc server has a TCP socket open an which it block-reads for "messages" from the vnc client, as soon as the client goes away the server will get an end of stream, which should tell it that the client has gone away.
Anyway, I think I am gonna handle this with the -IdleTimeout Xvnc argument. The IdleTimeout refers to inactivity in both directions, right? -nik > > Nik, > > > The solution I'd like, however, is that Xvnc terminates as > soon as the > > other endpoint (the machine that runs vncviewer) goes away (as in - > > network cable is unplugged). I am surprised that this does > not happen, > > especially if the vncviewer-Xvnc is a TCP connection. > > Why are you surprised? Is there some feature of TCP that > we're not aware of that would allow it to detect that the > computer running the computer was no longer accessible? > > Wez @ RealVNC Ltd. > > > Confidentiality Notice This e-mail (including any attachments) is intended only for the recipients named above. It may contain confidential or privileged information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please notify the sender of that fact and delete the e-mail from your system. _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
