On Tue, May 3, 2016 at 5:53 AM, Jesus Linares <[email protected]> wrote: > Hi, > > it seems that full command cannot be used in the agent.conf: > > command and full_command cannot be used in the agent.conf, and must be > configured in each system’s ossec.conf. (Documentation). > > I'll check it. >
Setting "logcollector.remote_commands" to 1 in internal_options.conf on the agent will allow it to run commands in the agent.conf. https://ossec.github.io/docs/syntax/head_internal_options.analysisd.html#intopt-logcollector.remote_commands=0 (I haven't read the thread, so this may be a silly respose) > Regards. > Jesus Linares. > > On Sunday, May 1, 2016 at 1:52:31 AM UTC+2, Robert Bardo wrote: >> >> Couple things I noticed.. >> >> I would use a .cmd, not .bat as I seem to vaguely remember a .cmd must be >> used.. it works now for me. >> >> Next, the shared command executable must be put in the server /shared >> directory and will be replicated to the correct client side folder. >> >> Lastly, why not use "auto OSSEC"? I had used it with much success. >> >> Cheers. Rob > > -- > > --- > 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. -- --- 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.
