X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=TODO;h=e60211a1e27fea9743065c93510aba55f423a1a3;hb=0a825b5cd4adb4d9dadfb2e237cdceae09399804;hp=d909ab9d87958c7341b648f56760ef1c9eb789e9;hpb=cde93897cdefdd7c7f66c400a61e42ceee5f6a46;p=elogind.git

diff --git a/TODO b/TODO
index d909ab9d8..e60211a1e 100644
--- a/TODO
+++ b/TODO
@@ -30,6 +30,8 @@ External:
 
 Features:
 
+* libsystemd-journal returns the object created as first param in sd_journal_new(), sd_bus_new() and suchlike as last...
+
 * cgroups:
   - implement system-wide DefaultCPUAccounting=1 switch (and similar for blockio, memory?)
   - implement per-slice CPUFairScheduling=1 switch
@@ -121,15 +123,14 @@ Features:
   - support "const" properties as flag
   - add API to clone sd_bus_message objects
   - SD_BUS_COMMENT() macro for inclusion in vtables, syntax inspired by gdbus
-  - make sd_bus_open_system_container() kdbus aware
-  - longer term:
-    * priority queues
-    * priority inheritance
   - sort out error codes for sd_bus_release_name(), distuingish: successful removal from foreign name, from non-existing name
-  - bug in kdbus: nameownerchange is not generated for names, only ids.
   - kdbus: matches against source or destination pids for an "strace -p"-like feel. Problem: The PID info needs to be available in userspace too...
   - kdbus: we need a way to distuingish messages we got due to monitoring from normal messages, since we want to bind methods only to the latter
   - figure out what to do when fields in the kdbus header and in the payload header do not match
+  - nameownerchange cannot be properly synthesized since we cannot distuingish messages from kernel when a name changed ownership starter → real from real → starter
+  - longer term:
+    * priority queues
+    * priority inheritance
 
 * sd-event
   - allow multiple signal handlers per signal
@@ -137,6 +138,7 @@ Features:
     but do not return anything up to the event loop caller. Instead
     add parameter to sd_event_request_quit() to take retval. This way
     errors rippling upwards are the option, not the default
+  - event sources should not be able to keep the sd_event around unconditionally
 
 * in the final killing spree, detect processes from the root directory, and
   complain loudly if they have argv[0][0] == '@' set.
@@ -310,7 +312,6 @@ Features:
     boot, and causes the journal to be moved back to /run on shutdown,
     so that we don't keep /var busy. This needs to happen synchronously,
     hence doing this via signals is not going to work.
-  - port to sd-event, enable watchdog from event loop
 
 * document:
   - document that deps in [Unit] sections ignore Alias= fileds in