ports/161524: Bug in the ossec-control script for server and local installs

Dan Parriott ddpbsd at gmail.com
Wed Oct 12 21:50:08 UTC 2011

>Number:         161524
>Category:       ports
>Synopsis:       Bug in the ossec-control script for server and local installs
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 12 21:50:08 UTC 2011
>Originator:     Dan Parriott
>Release:        8.2
OSSEC project
FreeBSD chusuk.example.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011     root at almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

There is a broken path in the ossec-control script. This bug was present in OSSEC's 2.6 release, and was fixed shortly after (no new release has been made though).
It's such a trivial fix there's no reason that I can think of not to include it.

Also in the pkg-message.in file a link to the wiki is included. The wiki may not be up to date, but the documentation is. A better link:

Run ossec-control start
patch attached to fix the ossec-control issue

Patch attached with submission follows:

--- src/init/ossec-server.sh.orig	2011-10-12 17:27:39.000000000 -0400
+++ src/init/ossec-server.sh	2011-10-12 17:27:50.000000000 -0400
@@ -206,7 +206,7 @@
     SDAEMONS="${DB_DAEMON} ${CSYSLOG_DAEMON} ${AGENTLESS_DAEMON} ossec-maild ossec-execd ossec-analysisd ossec-logcollector ossec-remoted ossec-syscheckd ossec-monitord"
     echo "Starting $NAME $VERSION (by $AUTHOR)..."
-    echo | ${DIR}/ossec-logtest > /dev/null 2>&1;
+    echo | ${DIR}/bin/ossec-logtest > /dev/null 2>&1;
     if [ ! $? = 0 ]; then
         echo "OSSEC analysisd: Testing rules failed. Configuration error. Exiting."


More information about the freebsd-ports-bugs mailing list