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 813e5f398cbf8bf78894128f109c0c81e05a1825..8520a97e42469e51f3a4f34d9e550fcfada600ec 100644 (file)
--- a/man/systemd-resolved.service.xml
+++ b/man/systemd-resolved.service.xml
@@ -36,7 +36,7 @@
     via three interfaces:</para>
 
     <itemizedlist>
-      <listitem><para>The native, fully-featured API <command>systemd-resolved</command> exposes on the bus,
+      <listitem><para>The native, fully-featured API <command>systemd-resolved</command> exposes via D-Bus,
       see
       <citerefentry><refentrytitle>org.freedesktop.resolve1</refentrytitle><manvolnum>5</manvolnum></citerefentry>
       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).</para></listitem>
 
+      <listitem><para>The native API <command>systemd-resolved</command> exposes via Varlink on the
+      <filename>/run/systemd/resolve/io.systemd.Resolve</filename> 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.</para></listitem>
+
       <listitem><para>The glibc
       <citerefentry project='man-pages'><refentrytitle>getaddrinfo</refentrytitle><manvolnum>3</manvolnum></citerefentry>
       API as defined by <ulink url="https://tools.ietf.org/html/rfc3493">RFC3493</ulink> and its related