mirror of
https://github.com/nmap/nmap.git
synced 2025-12-17 05:09:00 +00:00
Use a space between the number and the unit in quantities like "500 ms" in the
Reference Guide. See http://physics.nist.gov/Pubs/SP811/sec07.html#7.2 for a section of an SI style guide with this rule.
This commit is contained in:
@@ -2193,8 +2193,8 @@ more likely to get through a firewall. Look at the maximum round trip
|
|||||||
time out of ten packets or so. You might want to double that for the
|
time out of ten packets or so. You might want to double that for the
|
||||||
<option>--initial-rtt-timeout</option> and triple or quadruple it for
|
<option>--initial-rtt-timeout</option> and triple or quadruple it for
|
||||||
the <option>--max-rtt-timeout</option>. I generally do not set the
|
the <option>--max-rtt-timeout</option>. I generally do not set the
|
||||||
maximum RTT below 100ms, no matter what the ping times are. Nor do I
|
maximum RTT below 100 ms, no matter what the ping times are. Nor do I
|
||||||
exceed 1000ms.</para>
|
exceed 1000 ms.</para>
|
||||||
|
|
||||||
<para><option>--min-rtt-timeout</option> is a rarely used option that
|
<para><option>--min-rtt-timeout</option> is a rarely used option that
|
||||||
could be useful when a network is so unreliable that even Nmap's
|
could be useful when a network is so unreliable that even Nmap's
|
||||||
@@ -2417,8 +2417,8 @@ wish to be, while leaving Nmap to pick the exact timing values. The
|
|||||||
templates also make some minor speed adjustments for which
|
templates also make some minor speed adjustments for which
|
||||||
fine-grained control options do not currently exist. For example,
|
fine-grained control options do not currently exist. For example,
|
||||||
<option>-T4</option> prohibits the dynamic scan delay from exceeding
|
<option>-T4</option> prohibits the dynamic scan delay from exceeding
|
||||||
10ms for TCP ports and <option>-T5</option> caps that value at 5
|
10 ms for TCP ports and <option>-T5</option> caps that value at 5 ms.
|
||||||
milliseconds. Templates can be used in combination with fine-grained
|
Templates can be used in combination with fine-grained
|
||||||
controls, and the fine-grained controls will you specify will take
|
controls, and the fine-grained controls will you specify will take
|
||||||
precedence over the timing template default for that parameter. I
|
precedence over the timing template default for that parameter. I
|
||||||
recommend using <option>-T4</option> when scanning reasonably modern
|
recommend using <option>-T4</option> when scanning reasonably modern
|
||||||
@@ -2458,7 +2458,7 @@ does the equivalent of <option>--max-rtt-timeout 1250
|
|||||||
to 10 milliseconds. <option>T5</option> does the equivalent of
|
to 10 milliseconds. <option>T5</option> does the equivalent of
|
||||||
<option>--max-rtt-timeout 300 --min-rtt-timeout 50
|
<option>--max-rtt-timeout 300 --min-rtt-timeout 50
|
||||||
--initial-rtt-timeout 250 --max-retries 2 --host-timeout 15m</option> as well as
|
--initial-rtt-timeout 250 --max-retries 2 --host-timeout 15m</option> as well as
|
||||||
setting the maximum TCP scan delay to 5ms.</para>
|
setting the maximum TCP scan delay to 5 ms.</para>
|
||||||
|
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|||||||
@@ -2483,7 +2483,7 @@ containing the returned data (or the case of a failure, an error message).</para
|
|||||||
Sets the time, in milliseconds, after which input and
|
Sets the time, in milliseconds, after which input and
|
||||||
output operations on a socket should time out and
|
output operations on a socket should time out and
|
||||||
return. The default value is 30,000 (30 seconds). The lowest
|
return. The default value is 30,000 (30 seconds). The lowest
|
||||||
allowed value is 10ms, since this is
|
allowed value is 10 ms, since this is
|
||||||
the granularity of NSE network I/O.
|
the granularity of NSE network I/O.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|||||||
Reference in New Issue
Block a user