Thank you Jb. I asked the group the question before I had installed the agent on my Linux host, so I thought the way to mannually execute the syscheck/rootcheck processes was to execute agent_control -r -u ,<id>. Now that I have the agent installed on the hybrid server, I see there is no agent_control command in the ossec-agent/ bin directory. With that, what is the most efficient way to run the agent syscheck/rootcheck processes on the agent? ... just restart the agent itself? On Wednesday, February 13, 2013 8:13:25 AM UTC-6, TWAD wrote:
> Hey There, > > I find myself in a situation where all hosts in our network must execute > syscheck and rootcheck through a manual process vs. a scheduled basis. And > when I say manual process, I mean each administrator must have the > capability/choice to run it at the least intrusive time of operations. We > will still execute both on startup, but thereafter, syscheck and rootcheck > must be executed manually. I understand this can be executed with > agent_control –r u <id>; however, the administrator does not outright know > the agent ID. Has anybody written a procedure that would accomplish this > manual task on *nix and/or Windows? > > > > If no, do you know of a way I can write this that ensures the task is > foolproof for the administrator? > > > > Thank you > -- --- 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/groups/opt_out.
