"Mink, Adrian (QB8692)" <[EMAIL PROTECTED]> writes:

> It was the jre processes associated with the GUI for it. It was
> defiantly the portscanner, when I limited the range to scan it
> stopped killing it. 

This kind of broken software is very frustrating: as the port scanner
kills it, Nessus has no chance to look at it.

We added check_ports.nasl for this.
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.

Reply via email to