Nmap Development mailing list archives
Re: Flushing output
From: magnus () linuxtag org (Nils Magnus)
Date: Sun, 8 May 2005 04:00:41 +0200
Re, On Sat, May 07, 2005 at 03:06:32PM +0000, grutz wrote:
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.
That's why I suggested some time ago to introduce a handler for SIGUSR1 or something that makes nmap flush all data on a current host (or set of target hosts) and move on to the next one. Regards, Nils Magnus Program-Chair LinuxTag 2005 Free Conference Program LinuxTag 2005: Where .com meets .org - magnus () linuxtag org _______________________________________________ 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)