Thread Starter
nickth
(@nickth)
Changing “Maximum execution time for each scan stage” to 15 seemed to do the trick. Maybe 15 should be set to the default option to help everyone prevent future headaches like this?
@nickth: Thanks for the response. We’ll take a look at this, though we have other improvements for the scanner in progress, too. Changing the time limit to 15 makes the scans slower, and is only needed on a small number of hosts, but some of the other changes may help so that it isn’t necessary.
Thanks!
-Matt R
Thread Starter
nickth
(@nickth)
Looking forward to the scanner improvements to resolve some bugginess. ETA?
I don’t have an exact date yet, but if you do still have any issues after the next two versions are released, please do post back here, since that will narrow down the possible remaining issues. Thanks!
-Matt R
