doc: documented forked mode

diff --git a/contrib/murmurhash3/murmurhash3.c b/contrib/murmurhash3/murmurhash3.c
index 223ced56a0121ce7978d50b9baef46a70863c209..06ed7d84bb81ffad3169413d732dd54b4bb6bbb8 100644 (file)
--- a/contrib/murmurhash3/murmurhash3.c
+++ b/contrib/murmurhash3/murmurhash3.c
@@ -1,7 +1,7 @@
 /* This is MurmurHash3. The original C++ code was placed in the public domain
  * by its author, Austin Appleby. */
 
-#include "libknot/internal/trie/murmurhash3.h"
+#include "murmurhash3.h"
 
 static inline uint32_t fmix(uint32_t h)
 {

diff --git a/daemon/README.rst b/daemon/README.rst
index 2dc6f1f632303f5136bf74cc2d3bce2f36d13d87..29b93998742ad68374fd59e1555627a3c6e8823e 100644 (file)
--- a/daemon/README.rst
+++ b/daemon/README.rst
@@ -34,6 +34,31 @@ You can load modules this way and use their properties to get information about
 .. role:: lua(code)
    :language: lua
 
+Running in forked mode
+----------------------
+
+The server can clone itself into multiple processes upon startup, this enables you to scale it on multiple cores.
+
+.. code-block:: bash
+
+       $ kresd -f 2 rundir > kresd.log
+
+.. note:: On recent Linux supporting ``SO_REUSEPORT`` (since 3.9, backported to RHEL 2.6.32) it is also able to bind to the same endpoint and distribute the load between the forked processes. If the kernel doesn't support it, you can still fork multiple processes on different ports, and do load balancing externally (on firewall or with `dnsdist <http://dnsdist.org/>`_).
+
+
+Notice it isn't interactive, but you can attach to the the consoles for each process, they are in ``rundir/tty/PID``.
+
+.. code-block:: bash
+
+       $ nc -U rundir/tty/3008 # or socat - UNIX-CONNECT:rundir/tty/3008
+       > cache.count()
+       53
+
+This is also a way to enumerate and test running instances, the list of files int ``tty`` correspond to list
+of running processes, and you can test the process for liveliness by connecting to the UNIX socket.
+
+.. warning:: This is very basic way to orchestrate multi-core deployments and doesn't scale in multi-node clusters. Keep an eye on the prepared ``hive`` module that is going to automate everything from service discovery to deployment and consistent configuration.
+
 Configuration
 =============