Here's an odd one for you. Three different systems.
One running Win2K3 Server on a quad Xeon, one running WinXP Pro x64 on a dual Athlon, one running Win2K3 Server x64 on a Core2 Duo. On all three, the OSSEC agent chewed up _minimum_ of 45% of the CPU cycles along with using /accessing lsass and services, accounting for the remaining 55%. This lead to 100% CPU utilization on all platforms. Ouch. Is there some trick to the client that I'm missing? Incompatibilities? Further debug data I can provide? Thanks, -- Ed Vazquez New: It comes in different colors from the previous version. 23 May 2007 13:54:40
smime.p7s
Description: S/MIME cryptographic signature
