From 6dc26177147f12ebba5a63ee3eecdfe6a815d0de Mon Sep 17 00:00:00 2001
From: abhishek <abhishek@e0a8ed71-7df4-0310-8962-fdc924857419>
Date: Sat, 20 Aug 2016 18:57:49 +0000
Subject: [PATCH] Documentation for script-timeout. Closes #385

---
 docs/refguide.xml | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/docs/refguide.xml b/docs/refguide.xml
index 9fba28c58..bf2203afa 100644
--- a/docs/refguide.xml
+++ b/docs/refguide.xml
@@ -2784,6 +2784,24 @@ for that host.</para>
         </listitem>
       </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>
         <term>
         <option>--scan-delay <replaceable>time</replaceable></option>;