1kresd.systemd(7)       Knot Resolver 5.4.2 Systemd Units      kresd.systemd(7)
2
3
4

NAME

6       kresd.systemd - managing Knot Resolver 5.4.2 through systemd.
7
8

SYNOPSIS

10       kresd@.service
11       kresd.target
12       system-kresd.slice
13
14

DESCRIPTION

16       This manual page describes how to manage kresd using systemd units.
17
18       QUICKSTART
19
20           systemctl start kresd@1 - single instance of kresd, responding on localhost
21
22       CONCURRENT DAEMONS
23
24       kresd  daemon  can be executed in multiple independent processes, which
25       are managed with systemd via systemd templates  (see  systemd.unit(5)).
26       Each  systemd  service  instance of kresd (kresd@.service) represents a
27       single, independent kresd process.
28
29       If you have more than one CPU core available, a  single  running  kresd
30       daemon will only be able to make use of one core at a time, leaving the
31       other cores idle.  If you want kresd to take advantage of all available
32       cores,  while  sharing  both  cache  and sockets, you should enable and
33       start as many instances of the kresd@.service as you have cores.  Typi‐
34       cally,  each instance is just named kresd@N.service, where N is a deci‐
35       mal number. For example, to enable and start 3 concurrent daemons:
36
37           systemctl enable --now kresd@1.service kresd@2.service kresd@3.service
38
39       The systemd-managed  kresd  service  set  is  grouped  in  the  system-
40       kresd.slice  slice.   The slice includes all running daemons (instances
41       of kresd@.service).
42
43

EXAMPLES

45       To start a single kresd instance and enable it at boot:
46           systemctl enable --now kresd@1.service
47
48       To restart (or stop) all running instances, you can use a glob  expres‐
49       sion.   Please  note  that  glob  can't  be used to start or enable in‐
50       stances.
51           systemctl restart 'kresd@*'
52
53       Bash users can also use Brace Expansion to enable or start multiple in‐
54       stances, instead of listing them manually.
55           systemctl enable --now kresd@{1..4}.service
56
57       To  start  all  enabled  kresd  daemons,  you can also use the provided
58       kresd.target:
59           systemctl start kresd.target
60
61
62

SEE ALSO

64       kresd(8),        systemd.unit(5),        https://knot-resolver.readthe‐
65       docs.io/en/v5.4.2/
66
67

AUTHORS

69       kresd developers are mentioned in the AUTHORS file in the distribution.
70
71
72
73CZ.NIC                            2021-10-13                  kresd.systemd(7)
Impressum