[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ossec-list] ossec startup
- To: ossec-list@xxxxxxxxx
- Subject: [ossec-list] ossec startup
- From: Pete <pete42@xxxxxxxxx>
- Date: Wed, 11 Apr 2007 08:58:22 -0400
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=WBnUzKImepxVP02CVZaUAiKVYmByXjE1Rz5RezhtXOfhZF+PSu674bef3MV7CDZ55cIq8CGuMWmyt5cGZDG9+giudfugxgJCX6aaa5cqFupk80P5MDBwqqfMjexKo3seyocGNU3xMFZ9z5Resq1B7FsRiW2gD427EU6cMWHTQvA=
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
OSSEC home |
Main Index |
Thread Index
OSSEC project: www.ossec.net.
Mailling list information: http://www.ossec.net/en/mailing_lists.html.