Thank you for the response. While it is not always over 60%, it is pretty much always over 40%. I have been watching it for about a day, and it bounces around between 40% and 75%.
I am running the agent on Windows Server 2003. Also, I did change the syscheck interval to every 12 hours instead of every two hours - but it doesn't seem to have helped. Any other ideas? Thanks very much! Terry Daniel Cid wrote: > > Hi Terry, > > Is the ossec cpu usage that high all the time? It should only go up > like that when you start ossec (since it will scan the file system > generating checksum of the files). Btw, > which version of Windows are you using? One think you can do to try to > minimize > that is to change the syscheck frequency (from every two hours) to every > day. > To do that, just edit ossec.conf and change > > <syscheck> > <!-- Frequency that syscheck is executed - default every 2 hours --> > <frequency>7200</frequency> > .. > </syscheck> > > to > > <syscheck> > <!-- Frequency that syscheck is executed - to every 24 hours --> > <frequency>86400</frequency> > .. > </syscheck> > > > Hope it helps. > > > -- > Daniel B. Cid > dcid ( at ) ossec.net > On 10/5/06, Terry Morreale <[EMAIL PROTECTED]> wrote: >> >> Folks, >> I have installed the Windows agent but am seeing CPU utilization by the >> ossec process at about 60%. Has anyone found a way to keep utilization >> lower, maybe around 10%? >> >> Thanks! >> Terry >> >> -- >> ------------------------------------------------------------------------------- >> >> >> Terry Morreale >> Applied Trust Engineering - www.atrust.com - 303.245.4507 >> Security - Performance - Availability - Incident Management >> >> > -- ------------------------------------------------------------------------------- Terry Morreale Applied Trust Engineering - www.atrust.com - 303.245.4507 Security - Performance - Availability - Incident Management
