Clarification on upstart-0.5 and dbus usage
yanegomi at gmail.com
Wed Jun 18 23:06:32 BST 2008
On Wed, Jun 18, 2008 at 2:29 PM, Scott James Remnant <scott at netsplit.com> wrote:
> On Wed, 2008-06-18 at 22:36 +0200, Matthias Urlichs wrote:
>> > While there is another, secret, way
>> Well, at minimum you'd need _some_ method to tell Upstart that the dbus
>> daemon has started up and may now be registered with. :-P
> Upstart starts the D-Bus daemon, it knows ;)
Ok, so the takeaway is:
D-Bus provides status info and is method of communication between a
given process and upstart.
Maybe where my "wonderment" comes from is will all apps that
previously were just able to communicate with sysv now have to
explicitly implement callbacks with upstart via C-api's (or D-bus
compatible methods) or can other, simpler methods like the sysv / BSD
"/etc/[init,rc].d/some_script status" method be supported too? Or
perhaps this point of view is different from what my group is looking
for (if a process tanks, restart it), which isn't supported out of the
box in the original sysv / BSD style of obtaining status.
-Garrett <-- just plain confused; needs specs =(...
More information about the upstart-devel