summaryrefslogtreecommitdiffstats
path: root/systemd
diff options
context:
space:
mode:
authorTomas Krizek <tomas.krizek@nic.cz>2020-01-13 16:03:28 +0100
committerTomas Krizek <tomas.krizek@nic.cz>2020-01-15 10:38:20 +0100
commitdb915f1e973c531f3fb7d815ceac063c219d3cdf (patch)
tree81a330a0863def3f6ec1cf4f04716e50cc8bc72a /systemd
parentdoc: improve ToC navigation (diff)
downloadknot-resolver-db915f1e973c531f3fb7d815ceac063c219d3cdf.tar.xz
knot-resolver-db915f1e973c531f3fb7d815ceac063c219d3cdf.zip
doc: add section about usage without systemd
- mention process management - describe privileges and capabilities which have to be configured - move garbage collector to this section, as is it enabled by default
Diffstat (limited to 'systemd')
-rw-r--r--systemd/multiinst.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/systemd/multiinst.rst b/systemd/multiinst.rst
index 3897f5e0..a2ca7bec 100644
--- a/systemd/multiinst.rst
+++ b/systemd/multiinst.rst
@@ -3,6 +3,9 @@
Multiple instances
==================
+.. note:: This section describes the usage of kresd when running under systemd.
+ For other uses, please refer to :ref:`usage-without-systemd`.
+
Knot Resolver can utilize multiple CPUs running in multiple independent instances (processes), where each process utilizes at most single CPU core on your machine. If your machine handles a lot of DNS traffic run multiple instances.
All instances typically share the same configuration and cache, and incomming queries are automatically distributed by operating system among all instances.