units: rely only on isolate to remove running services when entering rescue/emergency...

[thirdparty/systemd.git] / fixme

* calendar time support in timer, iCalendar semantics for the timer stuff (RFC2445)

* complete dbus exposure

* implicitly import "defaults" settings file into all types

* add #ifdefs for non-sysv builds

* reinvestigate random seed, hwclock

* "disabled" load state?

* ability to kill services? i.e. in contrast to stopping them, go directly
  into killing mode?

* port over to LISTEN_FDS/LISTEN_PID:

   - uuidd    DONE
   - nscd     DONE
   - 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!)
   - distccd

* write utmp record a la upstart for processes

* follow property change dbus spec

* selinux

* systemctl status $PID, systemctl stop $PID!

* sulogin in den single user mode, mit plymouth --hide davor

External:

* patch /etc/init.d/functions with:

  if [ $PPID -ne 1 && mountpoint /cgroup/systemd ] ; then echo "You suck!" ; fi

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

* %m in printf() instead of strerror();