D-Bus User Bus

Havoc Pennington hp at pobox.com
Wed May 19 10:58:31 PDT 2010


2010/5/19 Colin Walters <walters at verbum.org>:
> Ah...this would require a lot of code changes.  For the keying+cron
> example above, both gnome-keyring would have to be changed to
> explicitly be a system-user service, and clients would have to be
> updated to look for org.gnome.Keyring.Uid500 etc.

But the user bus requires changes to *everything* - every single
service (or most of them) would suddenly require DISPLAY scoping?

ssh sessions should just have their own session bus, imo.

for cron accessing gnome-keyring - what is cron doing? can you explain
the use-case more? it really does seem like a system service though.
why start a whole "session" for that... if the goal is to let certain
per-user services to be available without a session or independent of
a session, then user-specific services on system bus seems kinda

If the goal is to access sessions from a systemwide thing, having each
session bus register with the system bus so a system service can
connect to the session bus, would be one approach. basically have a
"list session bus addresses for uid" method on system bus.


More information about the dbus mailing list