Having recently installed VNC 3.3.3r2 with the tight VNC patch
vnc-3.3.3r2-unix-tight-1.2.2.patch, we are running into a fairly frequent
problem where Xvnc consumes a lot of CPU time. This appears to be due to a
tight polling loop involving:
=>[1] _poll(0x0, 0x8, 0x0, 0x0, 0x0, 0x80), at 0xff217e74
[2] _select(0x7, 0x0, 0xff239164, 0xff239164, 0xffbeee38, 0xffbeed68), at
0xff1cb588
[3] httpCheckFds(0x1, 0x18e400, 0x179988, 0x0, 0x0, 0xffbeeea1), at 0xa41bc
[4] ProcessInputEvents(0x1, 0x179984, 0x179988, 0x0, 0x199ff0, 0x0), at
0x94494
[5] Dispatch(0x3ffffc, 0x175000, 0x94, 0x4, 0x198c00, 0x198d80), at 0x3a33c
[6] main(0x158400, 0x18e400, 0xffbef28c, 0x14, 0x198c00, 0x175000), at 0x28550
We do not normally use the HTTP access mechanism, so my first hack is going to
be to turn it off and see if that helps. However, if anyone can shed any light
on this I'd be grateful.
Oh yeah: this is on a Sparc Solaris 8 system, compiled with the SUN C compiler.
Thanks.
Bob Bramwell 403/294-6528 voice #860, 815-8 Av SW
Network Administrator 403/266-2620 fax Calgary, Alberta
Simulutions, a division of TCEnet Inc. T2P 3P2, Canada.
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
