> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Padraig Brady > Padraig Brady wrote: > > Hmm my vncserver just went into a tight loop (after about > > 5 days uptime and no connections within those 5 days)? > > > > $ rpm -q vnc > > vnc-3.3.3r2-28 > > > > # strace -p `pidof Xvnc` > > time(NULL) = 1039517461 > > select(128, [0 1 3 4 6 7 8 9 10 11 12 16 17 18 19 20], > NULL, NULL, {0,0}) = 0 (Timeout) > > select(22, [3], NULL, NULL, {0, 0}) = 0 (Timeout) > > select(5, [4], NULL, NULL, {0, 0}) = 0 (Timeout) > > gettimeofday({1039517461, 986137}, NULL) = 0 > > <above 5 calls repeated for ever ...> > > Hmm looks like this was seen before: > http://www.realvnc.com/pipermail/vnc-list/2002-November/034638.html > His was RH7.2, vnc-3.3.3r2-18 and mine RH7.3, vnc-3.3.3r2-28. > Note I'm pretty sure the time didn't change in the last > 5 days and definitely not around when the tight loop was entered. > > thanks, > Padraig.
I would suggest submitting this to bugzilla ( http://bugzilla.redhat.com ). I don't see any bugs present mentioning it. Redhat's version of VNC is a combination of TightVNC and the original ORL VNC. As you can also see it is behind the version on www.realvnc.com . You can try replacing the Redhat version with the RealVNC (or TightVNC if so inclined) one and see if the problem persists. If it doesn't you can submit it to bugzilla so that RedHat can get their version of VNC fixed. -- William Hooper _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
