Stephen, There was a bug in the standard X server codebase involving internal timers getting "lost" if they were active when an internal tick count rolled over every ~48 days. You're running an old version of VNC server, so it's quite possible that this is the problem you're seeing.
Can you upgrade to the current release and see how that works for you? Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Fromm > Sent: 12 September 2006 02:30 > To: [email protected] > Subject: VNC servers growing stale, slow > > We connect to a Solaris 5.9 box from MS Windows machines via > VNC. VNC > servers on Solaris box are realvnc v. 4.0; VNC viewers are > various versions, > mostly 4.0 and 4.2 though. > > I've used VNC for years, and occasionally a bug will be > manifest whereby if > a server has been running for long enough (usually months, > perhaps weeks), > it gets "stale" and is very slow, or even frozen. I've never > looked into it > enough to know why this happens, to what extent it's an > identified bug in > VNC (versus something in X, etc). > > Now, however, even fairly newly created servers are getting > stale. There > doesn't seem to be much rhyme or reason whether a server goes > stale or not; > some don't seem to, others do. > > My guess is that this isn't a VNC bug, but a problem with the > Solaris box > (probably software), though for all I know it could be a > network problem. > > How do I go about troubleshooting this? (I peeked in some of > the VNC server > logs and didn't see anything of interest.) > > TIA, > > S > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
