From: Vladimír Čunát Date: Fri, 3 May 2024 07:40:49 +0000 (+0200) Subject: doc/user/gettingstarted-startup.rst: less strong formulation X-Git-Tag: v6.0.12~2^2~9 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6cdbde634616a32f303a60d246b05216f8cd1725;p=thirdparty%2Fknot-resolver.git doc/user/gettingstarted-startup.rst: less strong formulation Some distros do enable knot-resolver.service on installation, e.g. I quickly tried in a CentOS 9 LXC where it didn't start immediately but it did after restarting the container. I believe that customs of each distro should be followed here. --- diff --git a/doc/user/gettingstarted-startup.rst b/doc/user/gettingstarted-startup.rst index b2680e9b4..e24b5c05b 100644 --- a/doc/user/gettingstarted-startup.rst +++ b/doc/user/gettingstarted-startup.rst @@ -16,7 +16,7 @@ See logs and status of running instance with ``systemctl status knot-resolver.se .. warning:: - ``knot-resolver.service`` is not enabled by default, thus Knot Resolver won't start automatically after reboot. + ``knot-resolver.service`` may not be enabled by default after installation, thus Knot Resolver might not start automatically after reboot. To start and enable service in one command use ``systemctl enable --now knot-resolver.service`` Unfortunately, for some cases (typically Docker and minimalistic systems), ``systemd`` is not available, therefore it is not possible to use ``knot-resolver.service``.