install: make systemd-install useful for installation of template instances

[elogind.git] / fixme

diff --git a/fixme b/fixme
index 57682f0ea8a8705f261d1ee370224cbcb621d819..7a0b499b475f7e9c74c69d4f621d99294c5802ef 100644 (file)
--- a/fixme
+++ b/fixme
@@ -1,4 +1,4 @@
-* timer
+* calendar time support in timer
 
 * enforce max number of concurrent connection limit in sockets.
 
@@ -8,11 +8,6 @@
 
 * implicitly import "defaults" settings file into all types
 
-* write .service file install tool
-    [Install]
-    WantedBy=graphical.target
-    Names=prefdm.service
-
 * service startup should be delayed if the matching socket is being started
 
 * add #ifdefs for non-redhat builds in sysv parser
@@ -33,8 +28,6 @@
 
 * iCalendar semantics for the timer stuff (RFC2445)
 
-* provide sysv-like command line utilities
-
 * ability to kill services? i.e. in contrast to stopping them, go directly
   into killing mode?
 
@@ -54,22 +47,30 @@
    - bluetoothd (/var/run/sdp! @/org/bluez/audio!)
    - distccd
 
-* regnerate unit/sysv search paths on daemon reload
-
 * write utmp record a la upstart for processes
 
-* run PAM session stuff
+* follow property change dbus spec
 
-* tcpwrap
+* pam module
 
-* use setproctitle() when forking, before exec() (waiting for (PR_SET_PROCTITLE_AREA to enter the kernel)
+* selinux
 
-* s/maintainance/maintenance/
+* User= and friends needs to understand %i and similar replacements
 
-* follow property change dbus spec
+* make systemd bus activatable
+
+* systemd-sysvinit as package
+
+* abstract namespace dbus socket
+
+* discuss NOTIFY_SOCKET, make it configurable? security implications?
+
+* when reading pid for watching, verify we are parent
 
 Regularly:
 
 * look for close() vs. close_nointr() vs. close_nointr_nofail()
 
 * check for strerror(r) instead of strerror(-r)
+
+* Use PR_SET_PROCTITLE_AREA if it becomes available in the kernel