OK --- I found the info on the Xvnc manpage. On the vncserver manpage it wasn't real obvious that I needed to also read the Xvnc manpage.
What was missing? I looked online to confirm, and the web documentation for WinVNC server covers IdleTimeOut:
http://www.realvnc.com/v4/winvnc.html#5
Or are you talking about them not specifically saying that options can be appended to the commandline on Windows? I don't recall seeing that either, but if you run winvnc4 -? note that it does give the options, including IdleTimeout.
The timeout is *VERY* annoying, BTW. Why was the default behavior changed?
That's an interesting point. I wasn't around for this, but I suspect it's a combination of things.
With more secure configurations that don't allow "new" connections to share or knock off "old" connections, if you drop connection by accident - modem disconnect, client crash, whatever - you would be completely locked out of the remote system. No way to connect until someone goes and reboots it or resets WinVNC indirectly, since WinVNC would wait for eternity assuming that the connection is still alive.
For a situation like yours, where connections are solid and you really DO want to stay connected, I think an actual keepalive or a "mouse wiggle" feature clientside would be a good idea. A developer would need to comment on this, though - this and the prior paragraph are wild guesses. _______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
