This message contains TMA Resources confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.What is your filename in /etc/rc3.d?
From: ossec-list@xxxxxxxxxxxxxxxx [mailto:ossec-list@xxxxxxxxxxxxxxxx] On Behalf Of Pete
Sent: Wednesday, April 11, 2007 8:58 AM
To: ossec-list@xxxxxxxxx
Subject: [ossec-list] ossec startup
Importance: Low
I wrote about this problem about a month ago, but I'm still having the same problem. In Solaris 9 and 10, ossec refuses to start automatically on startup. Here is what I've tried, maybe someone out there has another idea?
Copying the ossec startup script to /etc/init.d and calling it from an entry in /etc/rc3.d i.e. /etc/init.d/ossec start
Starting ossec directly from /etc/rc3.d i.e. /var/ossec/bin/ossec-control start
Using an intermediate script between rc3.d and /var/ossec/bin
None of these work, but once the server is started, I can start it from scripts all day long. The only thing that makes sense to me is that for some reason ossec cannot run at the rc3 run level. Any help out there would be greatly appreciated.
Pete