On Sat, 28 Sep 2002, Renaud Deraison wrote: > On Fri, Sep 27, 2002 at 06:28:52PM -0400, Kristofer T. Karas wrote: > > port = scanner_get_port(i) > > is not getting itself into an infinite loop somehow. This lockup only > > appears periodically, so perhaps it does depend upon which ports were or > > were not found open/closed when rescanned??? > > Which port range did you enter in the GUI ?
Gotcha. I myself wondered several times why check_ports.nasl (and its buddy port_shell_execution.nasl) spends so much time burning CPU cycles without any network activity (*). Sometimes, not always -- and it might correspond to the cases when I ran Nessus with a large set of scanned ports (maybe even 1-65535). (*) Apparently, my understanding of scanner_get_port() was wrong because I supposed it returns open ports only. --Pavel Kankovsky aka Peak "Welcome to the Czech Republic. Bring your own lifeboats." - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
