Hi,
Well, it certainly looks as if your xinetd daemon is not active at all. Did you see if anything was in the /var/log/messages file ? for example try a xinetd restart then do :
tail /var/log/messages
If there's nothing there, you might want to try verifying the rpm to see if any files are missing :
rpm -V xinetd
You will most-likely get some output saying that timestamps are different or whatever but make sure there is nothing missing. The rpm verification output is explained here -->
.
If in doubt, there is no harm in re-installing xinetd with the --replacepkgs option, i.e.:
rpm -Uvh --replacepkgs xinetd*.rpm
(assumes you are in the directory where the xinetd rpm file is - CD or whatever)
You could see if there are any xinetd files left lying around in /var/run (e.g. pid file). Try deleteing thiose.
Other than that I'd guess that there is a problem with one of the services. On redhat, the various config files are located in the directory /etc/xinetd.d and the main config file just includes the whole subdirectory. You can try turning off all your xinetd services except something like finger and see if it works....
/sbin/chkconfig --list
The bottom part of the response from the above command shows the xinetd controlled services - i.e. where it just says off or on. (The ones above with the numbers 1 to 6 are sysv controlled processes.) To turn-off services just do :
/sbin/chkconfig telnet off
(etc.)
Experiment with only enabling one or two services and see if xinetd then starts - if so there may be a corruption in one of the config files.
Hope this helps