15 Jun
2009
15 Jun
'09
4:54 p.m.
On Mon, 15.06.09 11:38, Fernando Lopez-Lezcano (nando(a)ccrma.Stanford.EDU) wrote:
[it'd be nice if you keep all the cc'ed original lists in the thread]
On Mon, 2009-06-15 at 19:34 +0200, Lennart Poettering wrote:
libdbus autospawns a session bus if none existant. It has been doing
that since quite some time.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
On Mon, 15.06.09 10:16, Fernando Lopez-Lezcano
(nando(a)ccrma.Stanford.EDU) wrote:
No. That use case does not make any sense. The D-Bus session bus is
autospawned if necessary these days.
So, let's say host A is where I am logged in now and I'm running a
desktop. The I start a terminal, just do "slogin B" (for simplicity
let's assume nobody is logged in into B at the time) and then I would
have dbus running there without a desktop? What is taking care of
setting up the dbus session, is that ssh? The login process?
Distributions will certainly enable the D-Bus code in JACK if they
ship it. So, I have no problem with depending on a dbus'ified jack for
this logic to work.
From a packagers' (for Fedora/Planet CCRMA)
point of view the future
dbus-capable jack should be able to be used without dbus
support as well
as with it _without_ having to recompile it (that is without having to
repackage it differently). For an example of non-dbus usage, I may want
to start jack on a remote host where there is no desktop session at the
moment and thus dbus is not usable.