mirror of
https://github.com/nmap/nmap.git
synced 2025-12-06 04:31:29 +00:00
Documentation for script-timeout. Closes #385
This commit is contained in:
@@ -2784,6 +2784,24 @@ for that host.</para>
|
|||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
<varlistentry>
|
||||||
|
<term>
|
||||||
|
<option>--script-timeout <replaceable>time</replaceable></option>
|
||||||
|
<indexterm><primary><option>--script-timeout</option></primary></indexterm>
|
||||||
|
</term>
|
||||||
|
<listitem>
|
||||||
|
|
||||||
|
<para>Some scripts take <emphasis>long</emphasis> time before they complete their execution, this can happen due to many reasons
|
||||||
|
maybe some bug in script, delay in the network or nature of the script itself(example:http-slowloris).
|
||||||
|
If you want to keep some limit on time for which script should run then you need to specify
|
||||||
|
<option>--script-timeout</option> with the maximum amount of time
|
||||||
|
for which script should be run. Note that all scripts will have same timeout. Once script gets timed out
|
||||||
|
no output for that script will be shown. Whether a script has timed out or not, can be seen in debug output.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>
|
<term>
|
||||||
<option>--scan-delay <replaceable>time</replaceable></option>;
|
<option>--scan-delay <replaceable>time</replaceable></option>;
|
||||||
|
|||||||
Reference in New Issue
Block a user