On Tue, Sep 6, 2016 at 7:01 AM, Daiyue Weng <[email protected]> wrote: > I did try restarting ossec, which should restart syscheckd as well Iguess? >
Yes. You can see the log messages related to syscheck in /var/ossec/logs/ossec.log. > On 6 September 2016 at 11:59, dan (ddp) <[email protected]> wrote: >> >> On Tue, Sep 6, 2016 at 6:36 AM, dan (ddp) <[email protected]> wrote: >> > On Sep 6, 2016 6:32 AM, "Daiyue Weng" <[email protected]> wrote: >> >> >> >> since I am running local-ossec, so agent_control doesn't do any good >> >> here? >> >> >> > >> > I'll install a local instance and try it out for you. I'll report back >> > shortly. >> > >> >> Not positive, but it doesn't look like it's working. I'm not keeping >> it around for another try. >> You may just have to restart the syscheckd process. >> -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
