resolve-host: use the usual log message when encountering a dbus parse failure

[elogind.git] / TODO

diff --git a/TODO b/TODO
index c7d61e94423977a5e50d7e91005617a19ad4be09..635071139c35d7ef3e70bde988e9de574c2cca85 100644 (file)
--- a/TODO
+++ b/TODO
@@ -24,6 +24,34 @@ External:
 
 Features:
 
+* libsystemd-network:
+  - I don't think there should be a client side object for dhcp
+    releases (probably not even a directory in /run for it)
+
+* resolved:
+  - IDN (?)
+  - DNSSEC
+  - LLMNR:
+        - do not fail daemon startup if socket is already busy (container)
+        - process incoming notification of conflict
+        - send notifications of conflict
+        - verify new RR uniqueness
+        - detect conflicts
+        - collect multiple responses
+        - jitter interval support
+        - add SOA record to empty responses
+  - mDNS/DNS-SD
+  - DNS-SD service registration from socket units
+  - port sd-resolve to direct bus calls
+  - nss module: fallback to glibc dns modules if resolved cannot be contacted
+  - edns0
+  - dname
+  - cname on PTR (?)
+
+* Ignore .busname units on classic D-Bus boots, systemd-resolved cannot be started on kdbus
+  without the active policy and should get a Wants=org.freedesktop.resolve1.busname to
+  pull-in the policy.
+
 * Allow multiple ExecStart= for all Type= settings, so that we can cover rescue.service nicely
 
 * the resolv.conf tmpfiles line should be covered by ENABLE_NETWORKD...
@@ -686,6 +714,9 @@ External:
 
 * register catalog database signature as file magic
 
+* zsh shell completion: <command> <verb> -<TAB> should complete options, but currently
+  does not
+
 Regularly:
 
 * look for close() vs. close_nointr() vs. close_nointr_nofail()