I recently began using Process Explorer from Sysinternals to monitor various aspects of a Windows system that happens to also be running the ossec agent. To my surprise, according to Process Explorer, ossec- agent.exe is BY FAR the heaviest I/O Reader of any process on the system, far more than the next heaviest read I/O process. This really surprises me--has anyone else seen this behavior? I fully expected the ossec-agent to be lightweight, so perhaps I've misconfigured something on my end?
- [ossec-list] ossec I/O reads Matt
- Re: [ossec-list] ossec I/O reads dan (ddp)
- Re: [ossec-list] ossec I/O reads Daniel Cid