diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-27 10:41:58 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-27 10:41:58 +0000 |
commit | 1852910ef0fd7393da62b88aee66ee092208748e (patch) | |
tree | ad3b659dbbe622b58a5bda4fe0b5e1d80eee9277 /doc/config-no-systemd-processes.rst | |
parent | Initial commit. (diff) | |
download | knot-resolver-upstream.tar.xz knot-resolver-upstream.zip |
Adding upstream version 5.3.1.upstream/5.3.1upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'doc/config-no-systemd-processes.rst')
-rw-r--r-- | doc/config-no-systemd-processes.rst | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/doc/config-no-systemd-processes.rst b/doc/config-no-systemd-processes.rst new file mode 100644 index 0000000..59aed1b --- /dev/null +++ b/doc/config-no-systemd-processes.rst @@ -0,0 +1,25 @@ +.. SPDX-License-Identifier: GPL-3.0-or-later + +Process management +================== + +There following should be taken into consideration when running without systemd: + +* To utilize multiple CPUs, kresd has to be executed as several independent + processes. +* Maintenance daemon(s) have to be executed separately. +* If a process crashes, it might be useful to restart it. +* Using some mechanism similar to :ref:`mod-watchdog` might be desirable to + recover in case a process becomes unresponsive. + +Please note, systemd isn't the only process manager and other solutions exist, +such as supervisord_. Configuring these is out of the scope of this +document. Please refer to their respective documentations. + +It is also possible to use kresd without any process management at all, which +may be suitable for some purposes (such as low-traffic local / home network resolver, +testing, development or debugging). + +.. include:: ../utils/cache_gc/README.rst + +.. _`supervisord`: http://supervisord.org/ |