Developers in my company are having problems with WebRoot creating excessively large log files due to endlessly scanning the executables they are building, testing and running.
This goes a bit beyond a regular exception policy, because the executables they create are of course literally brand new every time they start them. I imagine this situation is common for software developers using WebRoot (if there are any), so can anyone point me to the best solution?
Best answer by DanP
View original