From Fedora Project Wiki
m (1 revision(s)) |
m (Fixed templates) |
||
| Line 1: | Line 1: | ||
{ | {{Draft}} | ||
[[Navigation(siblings)] | [[Navigation(siblings)] | ||
| Line 9: | Line 6: | ||
As mentioned in [[FCNewInit/RC| Changes to RC]] , a DBUS service can read the system state from /var/run/services/. It can also use the initscripts of the services to gain more information about the status. | As mentioned in [[FCNewInit/RC| Changes to RC]] , a DBUS service can read the system state from /var/run/services/. It can also use the initscripts of the services to gain more information about the status. | ||
== See also == | == See also == | ||
[[../| Fedora New Init System]] | [[../| Fedora New Init System]] | ||
[[Navigation(siblings)] | [[Navigation(siblings)] | ||
== Comments == | == Comments == | ||
Latest revision as of 02:12, 3 June 2008
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
It is still under construction and content may change. Do not rely on the information on this page.
[[Navigation(siblings)]
DBUS Support for the Fedora New Init System
As mentioned in Changes to RC , a DBUS service can read the system state from /var/run/services/. It can also use the initscripts of the services to gain more information about the status.
See also
Fedora New Init System [[Navigation(siblings)]
Comments
The most important change wrt. to DBus and init is that DBus needs to gain support for activation on the system bus. Then we can move a lot of hardware-specific daemons that are blindly started right now to an on-demand activation. System bus activation is being reviewed on the DBus mailing list here