Leaking autolaunched busses

Doug Goldstein cardoe at gentoo.org
Sat Dec 16 10:32:17 PST 2006

John (J5) Palmieri wrote:
> The autolaunch code is pretty useful for when you log into another user
> in a terminal and run an app that requires D-Bus.  Unfortunately all of
> these busses are tied to the X session so if you log in as 100 users you
> get 100 busses and logging out of that user does not close them.
> Autolaunched busses should be smart enough to close themselves on a
> timeout if there are no apps attached to it (apps like gnome-vfs should
> be smart enough to know no one is talking to it and exit after a timeout
> so they don't block the bus).  It is not a huge issue but we should fix
> it at least in the development version.

I noticed this as well yesterday and was going to come up with a patch
that does exactly that. The only issue I foresaw was for example at the
computer lab for the CS students, they have SUSE machines where you can
lock your session and walk away. When you do, it allows another user to
walk up and login. What happens if the first session user isn't running
any D-Bus aware apps and leaves. Then when the 2nd user leaves, the 1st
user returns and tries to run a D-Bus aware app. Would that session bus
have timed out and gone away?

Doug Goldstein <cardoe at gentoo.org>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.freedesktop.org/archives/dbus/attachments/20061216/d46772b2/signature.pgp

More information about the dbus mailing list