picnoir
/
Systemd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fixme: minor updates

This commit is contained in:
Lennart Poettering 2010-02-14 22:45:08 +01:00
parent debf93a4d6
commit 874aa2cc72
1 changed files with 6 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
fixme
View File

@ -1,5 +1,5 @@
- mounts might take time, need to be executed asynchronously in a forked process? - trigger mounting; mounts might take time, need to be executed asynchronously in a forked process?
- need gc for active jobs that nothing cares for - need gc for active jobs that nothing cares for
@ -7,22 +7,14 @@
- refreshing of units (i.e. reload config files) - refreshing of units (i.e. reload config files)
- dbusification - further dbusification (i.e. export dependency information, per-unit-type data)
- cgroupsification - cgroupsification
- udev hookup
- snapshot system - snapshot system
- hookup with battery status, suspend/resume
- add a job mode which shuts everything down but what is requested - add a job mode which shuts everything down but what is requested
- implement priv dropping
- allow to disable priv dropping for hook scripts from fragment
- implement timer - implement timer
- implement automount - implement automount
@ -35,8 +27,6 @@
- verify fragment data after loading: refuse cycles on yourself, service units contradicting, more than one Start executable, ... - verify fragment data after loading: refuse cycles on yourself, service units contradicting, more than one Start executable, ...
- automatically delete stale unix sockets
- .socket needs to be notified not only by .service state changes, but also unsuccessful start jobs - .socket needs to be notified not only by .service state changes, but also unsuccessful start jobs
- we probably cannot use glibc's syslog() for logging, since it - we probably cannot use glibc's syslog() for logging, since it
@ -51,7 +41,7 @@
- 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? into killing mode?
- restart-on-success, restart-on-failure, restart-on-abort - 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:
@ -61,7 +51,7 @@
- dbus - dbus
- rsyslog - rsyslog
- cups - cups
- ssh - ssh CLASSIC
- postfix, saslauthd - postfix, saslauthd
- apache/samba - apache/samba
- libvirtd (/var/run/libvirt/libvirt-sock-ro) - libvirtd (/var/run/libvirt/libvirt-sock-ro)
@ -72,3 +62,5 @@
- teach dbus to talk to systemd when autospawning services - teach dbus to talk to systemd when autospawning services
- unix sockets chown()/chgrp() - unix sockets chown()/chgrp()
- watch dbus names for figuring out when a service has finished startup/goes down