summaryrefslogtreecommitdiff
path: root/man/systemd-resolved.service.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-04-24 21:04:43 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-05-05 22:41:23 +0200
commit1a0e562a5b367bbf01bc7532ca0f371e1dd38f48 (patch)
treeb5fed3a5408b47f454f6eec2288d484bb33a76dc /man/systemd-resolved.service.xml
parent81e06775be4d8394d0d8b1506adeee038343e4b9 (diff)
downloadsystemd-1a0e562a5b367bbf01bc7532ca0f371e1dd38f48.tar.gz
man: add description of org.freedesktop.LogControl1
I'm not sure if the LogTarget property is sufficiently general to be made into a property that can be generally implemented. It is very closely tied to the internal systemd logic. The other two seem fine thoough.
Diffstat (limited to 'man/systemd-resolved.service.xml')
-rw-r--r--man/systemd-resolved.service.xml2
1 files changed, 2 insertions, 0 deletions
diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
index 2f4efab1ff..6e1ee9f4a5 100644
--- a/man/systemd-resolved.service.xml
+++ b/man/systemd-resolved.service.xml
@@ -38,6 +38,8 @@
<listitem><para>The native, fully-featured API <command>systemd-resolved</command> exposes on the bus,
see
<citerefentry><refentrytitle>org.freedesktop.resolve1</refentrytitle><manvolnum>5</manvolnum></citerefentry>
+ and
+ <citerefentry><refentrytitle>org.freedesktop.LogControl1</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details. Usage of this API is generally recommended to clients as it is asynchronous and fully
featured (for example, properly returns DNSSEC validation status and interface scope for addresses as
necessary for supporting link-local networking).</para></listitem>