[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nmap-dev
Subject:    Re: Stupid patch... autostat every x seconds
From:       David Fifield <david () bamsoftware ! com>
Date:       2009-02-24 0:24:51
Message-ID: 20090224002450.GG18510 () gusto
[Download RAW message or body]

On Mon, Feb 16, 2009 at 05:52:12PM -0700, David Fifield wrote:
> On Tue, Jan 06, 2009 at 10:28:33PM +0100, Aleksandar Petrinic wrote:
> > Now I have write a very little patch for nmap that enables another option...
> > --auto-stats <seconds> that print a stats every <seconds> seconds.
> > I don't know if it could be usefull for someone, but I have tried. The diff
> > is in the attachment.
> > 
> > Well, maybe it's not the cleaner, but works(it isn't much accurate too). One
> > thing that confuse me it's where I have to put a temporary global variable,
> > for now I put it in the NmapOps, even if I immagine that it's not properly
> > the right place. With this patch I can syncronize a progress bar with nmap's
> > stats fine.
> 
> I made another patch, based on yours, with a few changes. I changed the
> option name to --stats-every. It takes a time specification like all the
> other timing options, defaulting to milliseconds and allowing a 's',
> 'm', 'h' suffix. This implementation only adds one new member to
> NmapOps. State is limited to the scope of one function. The scheduler is
> accurate. Output goes all the same places it normally goes when you
> press a key, including XML output.

I committed this in r12271. Thanks Aleksandar, your patch had the key
idea to make this possible.

David Fifield

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
[prev in list] [next in list] [prev in thread] [next in thread]