Clarification on upstart-0.5 and dbus usage

Matthias Urlichs smurf at
Wed Jun 18 21:52:25 BST 2008


Marcel Holtmann:
> Also using the D-Bus direct communication put the requirement on Upstart
> to become a D-Bus server and to message dispatching. This will bloat
> Upstart.

Umm, I would only use this direct socket for direct control
(i.e. request in => response out; no monitoring or other fancyness).

For that use case, the additional coding effort /complexity to support
direct communication is negligible.

> > 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
> Why? If Upstart starts the D-Bus system bus daemon, it knows, when it is
> there. Why bother with external tools.
There's a nontrivial but variable time between launching the daemon and
the moment this daemon opens its listening socket.

Matthias Urlichs   |   {M:U} IT Design @   |  smurf at
Disclaimer: The quote was selected randomly. Really. |
 - -
If a jury in a criminal trial stays out for more than twenty-four hours, it
is certain to vote acquittal, save in those instances where it votes guilty.
		-- Joseph C. Goulden

More information about the upstart-devel mailing list