From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6

Description of problem:
xinetd crashes on system boot, with the following in /var/log/messages:

Jul 26 00:08:05 localhost xinetd[2703]: 2703 {general_handler} (2703) Unexpected signal: 11 (Segmentation fault)
Jul 26 00:08:05 localhost last message repeated 9 times
Jul 26 00:08:05 localhost xinetd[2703]: 2703 {bad_signal} Received 10 signals in 1 seconds. Exiting...

Restarting xinetd after the system boots corrects the problem -- xinetd then functions normally.

Nothing is reported in the audit lot or in dmesg.



Version-Release number of selected component (if applicable):
xinetd-2.3.13-6

How reproducible:
Always

Steps to Reproduce:
1.reboot the machine
2.
3.
  

Actual Results:  The xinetd is not running.  The xinetd pid file exists, though.

Expected Results:  The xinetd process should be running normally.

Additional info:

There is one service enabled for xinetd on this system:

  # chkconfig --list | grep xinetd
  ...
  xinetd based services:
          bitlbee:        on
  ...

This is the bitlbee RPM compiled from the DAG repository.  The success or failure of the xinetd startup should not depend on bitlbee.  In any case, here is the xinetd entry for bitlbee:

  service ircd
  {
  disable = no
          socket_type     = stream
          protocol        = tcp
          wait            = no
          user            = daemon
          server          = /usr/sbin/bitlbee
          port            = 6667
          log_on_failure  += USERID
  }