Nmap Development mailing list archives
Flushing output
From: grutz <grutz () jingojango net>
Date: Sat, 07 May 2005 15:06:32 +0000
Here's something I'd like to see added that would help with rate-limited testing: really flushing out all the information nmap currently has about a host when interrupted with a SIGINT. It sucks to have been scanning 65535 ports on a subnet of 4 machines, have 3 of them be completed while one just sort of sits there, slowly responding. If you send nmap a SIGINT (^C) while it's hung on the last machine you don't get any information in the output other than the scan info. Now you have to rescan the previous hosts again. This primarily is a problem when scanning with the Nessus nmap plugin. Typically we recognize the slowdown, kill nmap and work around the slowed system. Since we also use a secondary nmap of all ports to help confirm the nessus data the lack of scan output for the other systems just adds more work. (oh and we're not billable since we're internal... >< ) _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev
Current thread:
- Flushing output grutz (May 07)
- Re: Flushing output Nils Magnus (May 07)
- Re: Flushing output Andreas Ericsson (May 08)
- Re: Flushing output Nils Magnus (May 07)