Nmap Development mailing list archives
Re: Inconcistent Nsock debug output
From: Daniel Miller <bonsaiviking () gmail com>
Date: Fri, 27 Mar 2015 12:45:30 -0500
On Fri, Mar 27, 2015 at 9:55 AM, Jacek Wielemborek <d33tah () gmail com> wrote:
Hi, Just a quick note - running "nmap -d9 scanme.nmap.org > debug.log" displays NSock debug output (related to rDNS) to stderr even though everything else gets redirected. I believe it would be better to unify that.
Agreed. Here are the things I see that are disparate: * nmap_nsock_stderr_logger in output.cc writes to LOG_STDERR (this is the source of the messages you're seeing.) * sleep_destructor in nse_nsock.cc writes to LOG_STDERR for -d >= 2 * log_error in nse_main.lua (implemented in l_log_write in nse_main.cc) writes to LOG_STDERR. * The general behavior for error, fatal, pfatal, and gh_perror defined in nmap_error.cc is to write to both: LOG_STDOUT | LOG_STDERR Related, the --log-errors option is a no-op since 29079. Sean Rivera removed it in GSOC 2012 under David's mentorship. Looking at that decision might give an idea of how to best handle this. Dan
_______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Inconcistent Nsock debug output Jacek Wielemborek (Mar 27)
- Re: Inconcistent Nsock debug output Daniel Miller (Mar 27)