You probably haven't enabled the linuxconf service, it isn't enabled by default.

There still is a real bug in the xinetd source rpm (xinetd-2.1.8.9pre11 of 
October 2000): In the source, a patch was not correctly applied - look at 
the .rej file for connection.c. Result of this bug is that a tcp wait service 
(as e.g. linuxconf) never can be restarted once the daemon exits. The fix is 
obvious.

There is no .rej files in the current version, and haven't been for some time
either... Still looking into the original problem.

*** Bug 18221 has been marked as a duplicate of this bug. ***

Still I wonder why this doesn't produce anything:

linuxconf --http
GET / HTTP/1.0

It seems that linuxconf hang somewhere in its code and waiting indefinitely. 
The same hang you can see if linuxconf is inoked by xinetd (with the same 
parameter).

Verified in qa0404, RH 7.0 has the same trouble (even upgrading xinetd & 
others).

Hmm, I tryed command line on RH 6.2 where WWW access via inetd works and 
linuxconf did not produxce any output too. So this seems that the bug may be 
inside xinetd as is written above. Sorry.

I tryed the wait patch from linuxconf guys. It makes linuconf work again. Here
it is:

--- xinetd-2.1.8.9pre14/xinetd/connection.c.orig	Mon Dec 11 00:57:11 2000
+++ xinetd-2.1.8.9pre14/xinetd/connection.c	Tue Apr 10 22:20:34 2001
@@ -86,8 +86,6 @@

	}
 #endif

-
	M_SET( cp->co_flags, COF_HAVE_ADDRESS ) ;
-
	M_SET( cp->co_flags, COF_NEW_DESCRIPTOR ) ;
 	}
 	else
 	{

The original of this patch can be found at:
ftp://ftp.solucorp.qc.ca/pub/misc/xinetd-wait.patch

Please, apply this patch if you can as this solve the problem with wait services
served by xinetd. I will attach this patch as an attachment to this bug.

Created attachment 15084 [details]
Wait patch for xinetd, diff against xinetd-2.1.8.9pre14-6 from qa0404's SRPMS.

I found this a couple of hours ago :)

The release with the fix is xinetd-2.1.8.9pre14-7, coming soon to Rawhide and
available now from http://people.redhat.com/teg/xinetd/

*** Bug 38221 has been marked as a duplicate of this bug. ***

*** Bug 39189 has been marked as a duplicate of this bug. ***

*** Bug 39189 has been marked as a duplicate of this bug. ***