[Merge] lp:~jamesodhunt/upstart/upstart-dbus-bridge into lp:upstart

[Steve Langasek]

On Thu, Jun 20, 2013 at 08:54:23PM -0000, Ted Gould wrote:
> Looking through this I don't see a way to specify which bus you want the
> event to come from.  So will there be two dbus bridges in the user
> session?  So I could do:

> start on dbus SENDER=foo

> or

> start on dbus-system SENDER=foo

> Not quite sure how that'll work.

An event emitted by the system dbus bridge will be seen by user upstart jobs
with the :sys: prefix.  Presumably we would just want a single bridge
running for the system bus, not one bridge per user for the system bus.

In that case, you would have:

  start on dbus SENDER=foo

for the session bus, or

  start on :sys:dbus SENDER=foo

for the system bus.

Though, I don't know how that squares performance-wise with --always, which
would presumably be needed at the system level since we don't have a way for
user init to subscribe to particular dbus events on the system bridge (and
shouldn't, for security reasons).

-- 
https://code.launchpad.net/~jamesodhunt/upstart/upstart-dbus-bridge/+merge/161772
Your team Upstart Reviewers is requested to review the proposed merge of lp:~jamesodhunt/upstart/upstart-dbus-bridge into lp:upstart.