This bug was fixed in the package vnc4 - 4.1.1+xorg4.3.0-37ubuntu3
---
vnc4 (4.1.1+xorg4.3.0-37ubuntu3) oneiric; urgency=low
* Fix 100% CPU hang when run from inetd in nowait mode if a client
connects and disconnects quickly (e.g., nmap). LP: #819473
- Added patch to debian
Patch also sent to Debian at http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=640158
** Bug watch added: Debian Bug tracker #640158
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640158
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I've tracked down the problem and implemented a fix. The issue is that
Xvnc in inetd mode detects whether it is run as "wait" or "nowait" by
checking if the inetd socket has a valid peer name with getpeername().
If it has a valid peer name then it assumes nowait mode, otherwise it
assumes wait mode
Also attaching my xinetd file for Xvnc.
** Attachment added: "/etc/xinetd.d/Xvnc"
https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/819473/+attachment/2247862/+files/Xvnc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Attachment added: "Xvnc-opreport2.txt"
https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/819473/+attachment/2247840/+files/Xvnc-opreport2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/8194
** Attachment added: "Xvnc-opreport.txt"
https://bugs.launchpad.net/bugs/819473/+attachment/2247835/+files/Xvnc-opreport.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819473
Title:
Xvnc cons
