On Fri, May 7, 2010 at 1:40 PM, Alex Eckelberry <[email protected]> wrote: > And yes, we do test each definition that go out. The problem with this one > was > that the loop condition kicks in on a file of a certain size that is not in > our test bed.
Would it be feasible to build some kind of governor into the scan-engine, such that if a scan on a single file takes more than a given amount of CPU time, the scan is assumed to have gone haywire, and will be throttled or killed? With suitable administrator alerts, of course. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
