DataProtector service not auto-started after server reboot

[Aaron Bliss]

I'm sure you already checked this, but is xinetd configured to start at
bootup?

Aaron

-----Original Message-----
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com]
On Behalf Of sunhux G
Sent: Monday, December 15, 2008 9:50 AM
To: General Red Hat Linux discussion list
Subject: DataProtector service not auto-started after server reboot

Hi

I have 5 Redhat 4.6  RHES servers which I've installed HP
dataprotector in exactly the same manner.

For 3 of them, each time after reboot the Dataprotector
"omni" process would listen on Tcp 5555 (netstat -a
confirms this)

However for 2 of them, DP "omni" is not auto-started up
after each reboot & I have to issue "service xinetd restart"
to start it up.

Can see that in all 5 servers,  /etc/xinetd.d/omni is present
& the contents are the same.


I've also created a startup script in /etc/rc3.d/S99startomni
& in /etc/rc5.d/S99startomni   which contain just one line :
service xinetd restart
but still after each reboot, it won't start up the omni service


What's wrong?  The 2 servers with problem was hardened
by an external vendor so not exactly sure what's been done


Thanks
Roger
-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list