.B \-s\fI <api_socket>\fR, \fB\-\-socket \fI<api_socket>
Specify how to connect to a running Knot Resolver. Accepts path to Unix-domain
-socket or \fIhost:port\fR. Defaults to \fI/var/run/knot-resolver/manager.sock\fR
+socket or \fIhost:port\fR. Defaults to \fI/var/run/knot-resolver/kres-api.sock\fR
Some commands do not require communication with the running resolver. In such
cases, the value of this option is ignored and the command may succeed even
* The JSON schema can be `downloaded here <_static/config.schema.json>`_ (valid only for the version of the resolver this documentation was generated for).
* The :ref:`kresctl schema <manager-client>` command outputs the JSON schema of the currently installed version as well. It does not require a running resolver.
-* The JSON schema can also be obtained from a running resolver by sending a HTTP GET request to the path ``/schema`` on the :ref:`management API <manager-api>` (by default a Unix socket at ``/var/run/knot-resolver/manager.sock``).
+* The JSON schema can also be obtained from a running resolver by sending a HTTP GET request to the path ``/schema`` on the :ref:`management API <manager-api>` (by default a Unix socket at ``/run/knot-resolver/kres-api.sock``).
.. tip::
===================
You can use HTTP API to dynamically change configuration of already running Knot Resolver.
-By default the API is configured as UNIX domain socket located in the resolver's rundir ``/var/run/knot-resolver/manager.sock``.
+By default the API is configured as UNIX domain socket located in the resolver's rundir ``/run/knot-resolver/kres-api.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:
If the :ref:`management <manager-api>` 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
+``/run/knot-resolver/kres-api.sock`` Unix-domain socket, which is the
Manager's default communication channel.
By default, ``kresctl`` tries to find the correct communication channel in
listen:
- interface: 127.0.0.1@53
management:
- unix-socket: /run/knot-resolver/manager.sock
+ unix-socket: /run/knot-resolver/kres-api.sock
set -e
-socket_opt="--unix-socket /var/run/knot-resolver/manager.sock"
+socket_opt="--unix-socket /run/knot-resolver/kres-api.sock"
echo " etag"
etag="$(curl --silent $socket_opt --fail http://localhost:5000/v1/config -o /dev/null -v 2>&1 | grep ETag | sed 's/< ETag: //;s/\s//')"
set -e
-curl --silent --fail --unix-socket /var/run/knot-resolver/manager.sock http://localhost/metrics > /dev/null
+curl --silent --fail --unix-socket /run/knot-resolver/kres-api.sock http://localhost/metrics > /dev/null
kresctl metrics
if [ "$?" -ne "0" ]; then