Why does my nrpe service need to be restarted manually?

[nagiosmaillist.4.lgetschel at spamgourmet.com]

All-
On _SOME_ of my RH systems after a reboot, the nrpe daemon doesn't show 
up as listening (netstat -pta | grep nrpe    doesn't show it).
But, if I restart xinetd, THEN the netstat shows nrpe is listening.

[root at ddclx09 root]# netstat -pta | grep nrpe
[root at ddclx09 root]# service xinetd restart
Stopping xinetd:                                           [  OK  ]
Starting xinetd:                                           [  OK  ]
[root at ddclx09 root]# netstat -pta | grep nrpe
tcp        0      0 *:nrpe                  *:*                     
LISTEN      4785/xinetd        
[root at ddclx09 root]#

I think the permissions are ok:
[root at ddclx09 etc]# ls -ld xinetd.d/
drwxr-xr-x    2 root     root         4096 Apr 23  2004 xinetd.d/
[root at ddclx09 etc]# ls -ld xinetd.d/nrpe
-rw-r--r--    1 root     root          480 Apr 23  2004 xinetd.d/nrpe

And it's in services:
[root at ddclx09 etc]# grep nrpe /etc/services
nrpe            5666/tcp                        # NRPE

Any suggestions on what is causing this to happen? and how to fix it?

Thanks,
Lewis

-- 
Lewis Getschel             | Today is done...
WesternGeco                |     Today was fun...
1625 Broadway              |         Tommorrow is another one.
Denver, CO 80202           |
Direct Phone - 303-389-4407|        -- Dr. Seuss --
(don't worry about the ... at spamgourmet.com email address, it's just a redirection service)




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null