Currently "chkconfig --list | grep -i omni" did not show "omni" is there.
I've tried "chkconfig --add omni" but when listing it out, it still won't show
omni service.
Can I do "chkconfig xinetd on" without turning on the other services because
they have been hardened & not supposed to be turned on (except omni which
I wanted)
Let me have the exact commands, thanks
Roger
On Mon, Dec 15, 2008 at 10:53 PM, Finnur Örn Guðmundsson <finnzi@xxxxxxxxxx> wrote:
sunhux G wrote:
Hi,------------------------------------------------------------------------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
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
Maybe you need to add xinetd to your startup: chkconfig xinetd on
Your S99* scripts are probably not executed, did you check if they have the executable bit set ?
Bgrds,
Finnur
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
