From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; AtHome0200)
Description of problem:
Attempting to connect to the linuxconf web services causes the "linuxconf -
-http" process to consume 100% CPU and the web client (lynx, netscape,
IE5) simply never receives any input (waiting for response). Must kill
the linuxconf --http process.
Steps to Reproduce:
1) Installed linuxconf from Redhat 7.1 CD
2) Enabled net access from linuxconf
3) Edited /etc/xinet.d/linuxconf and set disable=no
4) Rebooted computer
5) Started: lynx localhost:98
Actual Results: See a "linuxconf --http" process from a: ps axu
The web client shows connected to HTTP server, waiting for response.
No response ever comes.
"linuxconf --http" process goes to 100% CPU usage
Expected Results: Expected to see linuxconf start page.
Went to xinetd web site at http://www.xinetd.org/ and downloaded the
latest sources: xinetd-220.127.116.11pre15-tar.gz
and did a
./configure --prefix=/usr --with-libwrap --with-loadavg
did a lynx localhost:98
and up came the linuxconf stuff
Some interesting info in the readme for xinetd:
Another attempt to fix the tcp wait condition. TCP wait services were
being accept()'d when they shouldn't. This caused services such as
linuxconf, which accept() their own connections, to fail.
Closing because we don't ship linuxconf anymore
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.