+* calendar time support in timer
-- trigger mounting; mounts might take time, need to be executed asynchronously in a forked process?
+* enforce max number of concurrent connection limit in sockets.
-- need gc for active jobs that nothing cares for
+* complete dbus exposure
-- need gc for units that are not referenced anymore
+* make conf parser work more like .desktop parsers
-- refreshing of units (i.e. reload config files)
+* implicitly import "defaults" settings file into all types
-- further dbusification (i.e. export dependency information, per-unit-type data)
+* service startup should be delayed if the matching socket is being started
-- cgroupsification
+* add #ifdefs for non-redhat builds in sysv parser
-- snapshot system
+* add #ifdefs for non-sysv builds
-- add a job mode which shuts everything down but what is requested
+* bootchart hookup
-- implement timer
+* reinvestigate random seed, hwclock
-- implement automount
+* "disabled" load state?
-- create session/pgroup for child processes? handle input on console properly? interactive fsck? interactive luks password?
+* uid are 32bit
-- fs namespaces
+* %m in printf() instead of strerror();
-- templating/instances
+* gc: don't reap broken services
-- verify fragment data after loading: refuse cycles on yourself, service units contradicting, more than one Start executable, ...
+* iCalendar semantics for the timer stuff (RFC2445)
-- .socket needs to be notified not only by .service state changes, but also unsuccessful start jobs
+* provide sysv-like command line utilities
-- we probably cannot use glibc's syslog() for logging, since it
- presumably uses the logging socket in blocking mode which might
- trigger a deadlock if syslog does not process the socket anymore
- (maybe because it is restarted) and the socket buffer is full.
-
-- in udev/mount if properties change we need to delete the old
- settings and install the new settings. Deleting the old settings is
- currently missing.
-
-- ability to kill services? i.e. in contrast to stopping them, go directly
+* ability to kill services? i.e. in contrast to stopping them, go directly
into killing mode?
-- restart-on-success, restart-on-failure, restart-on-abort, restart-on-name-gnone
-
-- port over to LISTEN_FDS/LISTEN_PID:
+* port over to LISTEN_FDS/LISTEN_PID:
- uuidd DONE
- nscd DONE
- - rpcbind (/var/run/rpcbind.sock!)
- - dbus
- - rsyslog
- - cups
+ - dbus DONE
+ - rsyslog DONE
+ - rpcbind (/var/run/rpcbind.sock!) DONE
+ - cups DONE
+ - avahi-daemon (/var/run/avahi-daemon/socket) DONE
- ssh CLASSIC
- postfix, saslauthd
- apache/samba
- libvirtd (/var/run/libvirt/libvirt-sock-ro)
- bluetoothd (/var/run/sdp! @/org/bluez/audio!)
- - avahi-daemon (/var/run/avahi-daemon/socket)
- 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
+
+Regularly:
-- unix sockets chown()/chgrp()
+* look for close() vs. close_nointr() vs. close_nointr_nofail()
-- watch dbus names for figuring out when a service has finished startup/goes down
+* check for strerror(r) instead of strerror(-r)
-- initialize console tty on startup
+* Use PR_SET_PROCTITLE_AREA if it becomes available in the kernel
~ianmdlvl / elogind.git / blobdiff