1
0
mirror of https://github.com/nmap/nmap.git synced 2026-01-06 14:39:03 +00:00
david e0250c1b66 Change the conditions for printing a timing status update to what I think they
were intended to be. We are okay to print if
  1. We don't have a completion time estimate yet; or
  2. We have passed the last completion time estimate; or
  3. The estimated time remaining differs from the last one printed by more
     than 3 minutes, and the difference accounts for more than 5% of the
     estimated total time.
The problem was that the last printed time remaining was calculated not as
difftime(last_est.tv_sec, last_print.tv_sec), but as
difftime(last_est.tv_sec, now->tv_sec). In other words it was constantly
changing, and at the same rate as the estimated time left (if the scan was
progressing at a constant rate). That means that as soon as a completion time
estimate was fairly accurate, you would not get any more estimates because the
difference in the two times would always be small.
2009-02-11 18:56:46 +00:00
2009-02-10 21:18:36 +00:00
2009-02-03 02:29:19 +00:00
2008-07-31 14:18:21 +00:00
2008-05-31 02:39:27 +00:00
2008-05-31 02:39:27 +00:00
2008-09-03 22:16:59 +00:00
2008-12-21 22:49:39 +00:00
2008-12-21 22:46:22 +00:00
2008-07-15 20:06:05 +00:00

Here is some documentation for Nmap, but these files are much less
comprehensive than what you'll find at the actual Nmap documentation
site ( http://nmap.org ).
Languages
C 37.8%
Lua 28.1%
C++ 16.7%
Shell 5.8%
Python 4.2%
Other 7.2%