doc: more info on unix socket rule reload

diff --git a/doc/userguide/rule-management/rule-reload.rst b/doc/userguide/rule-management/rule-reload.rst
index a857a21197de828e87a91707d82ad701711127d9..a73c5cecadfc06b126fd71d98dc4b7247f4285f9 100644 (file)
--- a/doc/userguide/rule-management/rule-reload.rst
+++ b/doc/userguide/rule-management/rule-reload.rst
@@ -18,6 +18,14 @@ Signal::
 
   kill -USR2 $(pidof suricata)
 
-Unix socket::
+Unix socket has two method for rules reload.
+
+Blocking reload ::
 
   suricatasc -c reload-rules
+
+Non blocking reload ::
+
+  suricatasc -c ruleset-reload-nonblocking
+
+It is also possible to get information about the last reload via dedicated commands. See :ref:`standard-unix-socket-commands` for more information.

diff --git a/doc/userguide/unix-socket.rst b/doc/userguide/unix-socket.rst
index 07694214908c5e961c70bf9c8adcbb36d768c106..aa11bde73726e1422fc56a0da1675690065b7a75 100644 (file)
--- a/doc/userguide/unix-socket.rst
+++ b/doc/userguide/unix-socket.rst
@@ -46,6 +46,8 @@ example to write custom scripts:
 * Perl: https://github.com/aflab/suricatac (a simple Perl client with interactive mode)
 * C: https://github.com/regit/SuricataC (a unix socket mode client in C without interactive mode)
 
+.. _standard-unix-socket-commands:
+
 Commands in standard running mode
 ---------------------------------
 You may need to install suricatasc if you have not done so, running the following command from scripts/suricatasc