Description of problem:

At random times, xinetd persistently segfaults whenever it tries to spawn 
a new process to start a service upon a new connection. It's not 
reproducible, in my experience it just happens at about 30 hours intervals.
The segfaulting is persistent, meaning that when this happens, every new 
process xinetd tries to spawn upon will crash. The amount of time during 
which this segfaulting persists will vary, from own experience it can be 
anywhere from 15 to 90 minutes at a time. You can stop this segfaulting 
behavior if you restart xinetd.
This problem applies to xinetd-2.3.0-1.71 from 7.1 Errata. I don't know if 
it applies to xinetd-2.1.8.9pre14-6 that comes with the 7.1 distribution.

Version-Release number of selected component (if applicable):
2.3.0-1.71

How reproducible:
Couldn't Reproduce

Steps to Reproduce:


Additional info:

While the segfaulting persists, upon every new connection to a xinetd 
service, a set of messages like the ones below is logged via syslog 
in /var/log/messages:

Aug 28 20:22:24 gaulois xinetd[21846]: {general_handler} (21846) 
Unexpected signal: 11 (Segmentation fault)
Aug 28 20:22:24 gaulois last message repeated 9 times
Aug 28 20:22:24 gaulois xinetd[21846]: {bad_signal} Received 10 signals in 
1 seconds. Exiting...

Suggestions:

In the "Recent Changes" changelog for xinetd available at 
http://www.xinetd.org/#changes, under version 2.3.1, I read:

* Attempt to fix segfaulting seen since 2.3.0. -Steve Grubb

I could not locate any other information regarding this issue on xinetd 
web site. I am not sure whether this fix refers to the same problem I am 
reporting and I do not know if the problem has been actually fixed since 
the 2.3.1 release, but perhaps it would be a good idea to release a new 
updated rpm with the latest version (2.3.2) in errata, since this version 
also fixes other important bugs.