Re: Monitor Ossec

[frwa onto]

Dear Werner,

                   So if we keep separate how will the monit executable will be able to read different .conf file? Ok I got it why you want to keep it separate it due to updates of monit. So since I am on the bad side what is your best advice here ? Any other method to simulate it.

On Tue, Sep 24, 2013 at 11:50 PM, Werner Flamme <address@hidden> wrote:

frwa onto [24.09.2013 17:21]:

> Dear Werner,
>                    I dont understand what is the need of the extra
> ossec.conf why not its in the main monit.conf ?

You can put anything you wrote into the separate file into monit.conf
(which I don't have, it's monitrc for me). The reason for keeping it
separated is that on an update, the central config may be rewritten, and
that your parts of the config might get lost. If you keep it in a
separate file, it will stay there even when you update monit.

> On Tue, Sep 24, 2013 at 11:19 PM, frwa onto <address@hidden> wrote:
>
>> Dear Werner,
>>                    I went into the man page here
>> http://mmonit.com/monit/documentation/monit.html#program_status_testing so
>> I read and change it to this now check program test_ossec  with path
>> "/usr/bin/test_ossec" with timeout 1000 seconds and still get service monit
>> start
>> Starting monit: /etc/monit.d/ossec.conf:1: Error: syntax error 'test_ossec'
>>                                                            [FAILED]
>>  . I think my problem why it does not recognize could it be due to my
>> monit version is  monit -V
>> This is monit version 5.1.1
>> Copyright (C) 2000-2010 by Tildeslash Ltd. All Rights Reserved. I am using
>> Centos 6.4 and epel repo. Another thing how I start the ossec is via the
>> /var/ossec/bin/ossec-control start not via the /etc/init.d scripts.

From what I found, "check program" must have been introduced with
version 5.3, so you are on the bad side here.

Regards,
Werner

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general