I don't think you can force it. You may be able to speed it up by restarting the ossec server processes. How long did you wait for it to update? It may take a while. You could also check the logs of those agents to see if anything about the agent.conf was logged.
On Tue, Jun 8, 2010 at 3:02 PM, ASR <[email protected]> wrote: > How to forcefully update the agent.conf on the client nodes? I have > couple of AIX servers that received the initial agent.conf file, but > subsequent updates to the file doesn't seem to reach the clients (MD5 > sum/client version is different). > Thanks, > Antony. >
