Re: Gsoc suggestion

[Robin Wood <robin () digininja org>]

On 16 March 2014 11:58, Daniel Miller <bonsaiviking () gmail com> wrote:
> Robin,
>
> In my experience, this is almost always related to an NSE script that is
> hanging. While not a solution, here is what I do to determine what is going
> on:
>
> First, make sure I can run nmap with terminal interaction, e.g. "sudo -s;
> nmap" vs "sudo nmap" (see this bug, still unfixed:
> http://seclists.org/nmap-dev/2012/q2/29). Then when I get to the "99%
> complete 1 second remaining" status, I press "d" to increase debugging to
> level 2. At debugging level 2, pressing any other key gives a status report
> that includes Lua stacktraces of all running NSE scripts. It can get very
> verbose, especially with the new-ish Nsock debugging output, so I don't do
> it normally, but it can be handy in a pinch.
>
> Dan

Useful to know.

Robin


> On Sun, Mar 16, 2014 at 3:18 AM, Robin Wood <robin () digininja org> wrote:
> > This is a tongue in cheek suggestion for a gsoc project but one that would
> > be great if done, improve the remaining time/time to finish feature.
> >
> > I'm sure there are plenty of documented reasons as to why it is hard to
> > estimate time but if someone could find a way to stop the 5 minutes of
> > "99%
> > complete 1 second remaining" it would be great.
> >
> > No where near as sexy as the other ideas but something that would benefit
> > every user.
> >
> > Robin
> > _______________________________________________
> > Sent through the dev mailing list
> > http://nmap.org/mailman/listinfo/dev
> > Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/