I think that some of the timeout handling in VNC is quite sensitive to
having things like NTP running. I have seen the idle timeout trigger
after only a few seconds' use, and have also seen the deferUpdate
timeout completely fail to trigger.
My theory is that NTP is stepping the time back when I've seen this
happen, and that there are incautious comparisons in the timeout code
in VNC.
How about making changes like the following?:
--- VNCSConnectionST.cxx.timeout 2003-09-03 18:05:01.000000000 +0100
+++ VNCSConnectionST.cxx 2003-09-03 18:07:54.000000000 +0100
@@ -206,7 +206,8 @@
if (state() != RFBSTATE_NORMAL && idleTimeout < 15)
idleTimeout = 15; // minimum of 15 seconds while authenticating
time_t now = time(0);
- int timeLeft = lastEventTime + idleTimeout - now;
+ unsigned int sincelast = now > lastEventTime ? now - lastEventTime : 0;
+ int timeLeft = idletimeout - sincelast;
if (timeLeft <= 0) {
close("Idle timeout");
return 0;
Tim.
*/
[demime 0.99d.1 removed an attachment of type application/pgp-signature]
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
