chiark
/
gitweb
/
~ianmdlvl
/
elogind.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
debf93a
)
fixme: minor updates
author
Lennart Poettering
<lennart@poettering.net>
Sun, 14 Feb 2010 21:45:08 +0000
(22:45 +0100)
committer
Lennart Poettering
<lennart@poettering.net>
Sun, 14 Feb 2010 21:45:08 +0000
(22:45 +0100)
fixme
patch
|
blob
|
history
diff --git
a/fixme
b/fixme
index 3ed5fdfa2c560f60e608f3f46455cae34cfd0e85..55df3be713cb193949389acf854f20fc277ce28d 100644
(file)
--- a/
fixme
+++ b/
fixme
@@
-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 automount
- implement timer
- 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
- we probably cannot use glibc's syslog() for logging, since it
- .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
@@
-51,7
+41,7
@@
- ability to kill services? i.e. in contrast to stopping them, go directly
into killing mode?
- 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-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
- rsyslog
- cups
- dbus
- rsyslog
- cups
- - ssh
+ - ssh
CLASSIC
- postfix, saslauthd
- apache/samba
- libvirtd (/var/run/libvirt/libvirt-sock-ro)
- postfix, saslauthd
- apache/samba
- libvirtd (/var/run/libvirt/libvirt-sock-ro)
@@
-72,3
+62,5
@@
- teach dbus to talk to systemd when autospawning services
- unix sockets chown()/chgrp()
- teach dbus to talk to systemd when autospawning services
- unix sockets chown()/chgrp()
+
+- watch dbus names for figuring out when a service has finished startup/goes down