From: Tomas Krizek <tomas.krizek@nic.cz>
Date: Thu, 31 May 2018 13:31:22 +0000 (+0200)
Subject: systemd: man page - update about system-kresd.slice
X-Git-Tag: v2.4.0~31^2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b9c6b876bfca3c23b46d1b09ed726d6613573bf4;p=thirdparty%2Fknot-resolver.git

systemd: man page - update about system-kresd.slice
---

diff --git a/doc/kresd.systemd.7 b/doc/kresd.systemd.7
index 0791165a2..4fbba04c7 100644
--- a/doc/kresd.systemd.7
+++ b/doc/kresd.systemd.7
@@ -101,6 +101,9 @@ number.  To enable 3 concurrent daemons:
 
 .B Using system-kresd.slice
 
+The following commands may not work with older systemd (e.g. on CentOS 7).
+See notes for more info.
+
 The easiest way to view the status of systemd-supervised \fBkresd\fR
 instances is to use the \fIsystem-kresd.slice\fR:
 
@@ -151,6 +154,12 @@ network interfaces for \fBkresd\fR in \fI/etc/knot-resolver/kresd.conf\fR.  The
 service can be started or enabled in the same way as in the examples below, but
 it doesn't have any sockets associated with it.
 
+.IP * 2
+Controlling the service with \fIsystem-kresd.slice\fR requires newer systemd.
+It may not work in some distributions, notably CentOS 7. To control multiple
+kresd instances, use \fIkresd@*.service\fR or \fIBrace Expansion\fR mentioned
+below.
+
 .SH "EXAMPLES"
 
 .B Single instance
@@ -203,7 +212,7 @@ To enable multiple concurrent daemons, for example 16:
 To start all enabled daemons:
 .nf
 .RS
-.B systemctl start 'kresd@*.service'
+.B systemctl start --all 'kresd@*.service'
 .RE
 .fi