systemctl: add compat support for shutting down the system via upstart

[elogind.git] / fixme

diff --git a/fixme b/fixme
index 08ba2dda1ba8b1710d6e68a9f475acbf172031b6..374ff4107e9c2211c234a409c456cd66daa176d1 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
@@ -23,8 +18,6 @@
 
 * reinvestigate random seed, hwclock
 
-* introduce serialized mode
-
 * "disabled" load state?
 
 * uid are 32bit
@@ -56,15 +49,38 @@
    - bluetoothd (/var/run/sdp! @/org/bluez/audio!)
    - distccd
 
-* teach dbus to talk to systemd when autospawning services
+* write utmp record a la upstart for processes
+
+* follow property change dbus spec
+
+* pam module
+
+* selinux
+
+* User= and friends needs to understand %i and similar replacements
+
+* make systemd bus activatable
 
-* Figure out which signal handlers we actually have to reset in the
-  forked off child
+* pin /cgroup/systemd
 
-* Add code to systemctl to wait for an operation to finish
+* systemd-sysvinit as package
+
+* install must understand templates
+
+* upstart fallback in systemctl
+
+* abstract namespace dbus socket
+
+* /sbin/shutdown argv[2..] message
+
+* exec /sbin/telinit from init
+
+* discuss NOTIFY_SOCKET, make it configurable? security implications?
 
 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