From: Oto Šťáva Date: Mon, 18 Sep 2023 07:35:20 +0000 (+0200) Subject: doc/manager-client: slight clarifications X-Git-Tag: v6.0.3~1^2~10 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0a96a270b14f7a821fe30accc2f695a2aaf2aa94;p=thirdparty%2Fknot-resolver.git doc/manager-client: slight clarifications --- diff --git a/doc/manager-api.rst b/doc/manager-api.rst index 0001824d2..7992d86a7 100644 --- a/doc/manager-api.rst +++ b/doc/manager-api.rst @@ -11,7 +11,7 @@ Management HTTP API =================== You can use HTTP API to dynamically change configuration of already running Knot Resolver. -By default the API is configured as UNIX domain socket ``manager.sock`` located in the resolver's rundir (typically ``/run/knot-resolver/``). +By default the API is configured as UNIX domain socket located in the resolver's rundir ``/var/run/knot-resolver/manager.sock``. This socket is used by ``kresctl`` utility in default. The API setting can be changed only in ``/etc/knot-resolver/config.yaml`` configuration file: diff --git a/doc/manager-client.rst b/doc/manager-client.rst index ddb1f695b..bb6597df5 100644 --- a/doc/manager-client.rst +++ b/doc/manager-client.rst @@ -30,9 +30,9 @@ the :option:`--config <-c , --config >` or :option:`--socket <-s , --socket >` option to tell ``kresctl`` where to look for the API. -If the ``management`` key is not present in the configuration file, ``kresctl`` -attempts to connect to the ``/var/run/knot-resolver/manager.sock`` Unix-domain -socket, which is the Manager's default communication channel. +If the :ref:`management ` key is not present in the configuration file, +``kresctl`` attempts to connect to the ``/var/run/knot-resolver/manager.sock`` +Unix-domain socket, which is the Manager's default communication channel. By default, ``kresctl`` tries to find the correct communication channel in ``/etc/knot-resolver/config.yaml``, or, if present, the file specified by the