From: Lennart Poettering Date: Mon, 4 Mar 2024 10:34:09 +0000 (+0100) Subject: resolved: mention the Varlink interface of resolved X-Git-Tag: v256-rc1~649 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=af8a03ccf863ddfa7823ad857681e23e54308070;p=thirdparty%2Fsystemd.git resolved: mention the Varlink interface of resolved This is ready from prime-time, hence mention it. --- diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml index 813e5f398cb..8520a97e424 100644 --- a/man/systemd-resolved.service.xml +++ b/man/systemd-resolved.service.xml @@ -36,7 +36,7 @@ via three interfaces: - The native, fully-featured API systemd-resolved exposes on the bus, + The native, fully-featured API systemd-resolved exposes via D-Bus, see org.freedesktop.resolve15 and @@ -45,6 +45,11 @@ featured (for example, properly returns DNSSEC validation status and interface scope for addresses as necessary for supporting link-local networking). + The native API systemd-resolved exposes via Varlink on the + /run/systemd/resolve/io.systemd.Resolve AF_UNIX socket. This provides similar + functionality as the D-Bus interface, but is available during the entire runtime, without requiring a + running D-Bus system bus broker service. + The glibc getaddrinfo3 API as defined by RFC3493 and its related