mirror of
https://github.com/nmap/nmap.git
synced 2026-08-04 06:40:48 +00:00
Remove the code that catches up the --max-rate scheduled send time to
the present. This allows the sending rate to temporarily exceed the maximum to keep from being slowed too much by other delays in the scan engine. See the discussion at http://seclists.org/nmap-dev/2008/q3/0236.html.
This commit is contained in:
parent
bbae5a7845
commit
227adcd664
2 changed files with 10 additions and 11 deletions
|
|
@ -2477,12 +2477,12 @@ seconds.</para>
|
|||
|
||||
<para><option>--max-rate</option>, like <option>--min-rate</option>, is
|
||||
a global option affecting an entire scan. It affects only port and host
|
||||
discovery scans. Unlike <option>--min-rate</option>, which is a
|
||||
<quote>best-effort</quote> option, <option>--max-rate</option> is a hard
|
||||
upper bound on the scanning rate.</para>
|
||||
discovery scans.</para>
|
||||
|
||||
<para>Nmap may go slower than the maximum rate if conditions require it.
|
||||
To keep the sending rate within a specified range, use
|
||||
<para>The sending rate may temporarily exceed the maximum to make up for
|
||||
unpredictable delays, but on average the rate will stay at or below the
|
||||
maximum. Nmap may go slower than the maximum rate if conditions require
|
||||
it. To keep the sending rate within a specified range, use
|
||||
<option>--min-rate</option> and <option>--max-rate</option>
|
||||
together.</para>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue