lifecycle of the message bus
Sriram Ramkrishna
sri@aracnet.com
Sun, 13 Jul 2003 12:08:15 -0700
I get the same problem out of CVS. I think it's something to do with
the default. THe session.conf file indicates that same directory
structure but nothing is populated there.
sri
On Sun, Jul 13, 2003 at 07:53:31PM +0100, Thomas Leonard wrote:
> On Tue, Apr 29, 2003 at 11:15:30AM -0400, Havoc Pennington wrote:
> [...]
> > dbus-babysitter connects to the X server and the listens for HUP on
> > the tty and exits the bus when either connection is lost.
>
> Did the X transport for DBUS ever get written? It seems that we'd always
> want it enabled for the session bus, so the server could use just that
> (without needing a babysitter).
>
> BTW, running configure with no arguments results in:
>
> $ dbus-launch
> Failed to start message bus: Failed to read directory
> "/usr/local/etc/dbus-1/NONE/lib/dbus-1.0/services": No such file or
> directory
>
> Also, the man page suggests:
> eval `dbus-launch --exit-with-session`
>
> but that command never returns (not closing stdout?)
>
>
> --
> Thomas Leonard http://rox.sourceforge.net
> tal00r@ecs.soton.ac.uk tal197@users.sourceforge.net
> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1
> --
> message-bus-list mailing list
> message-bus-list@freedesktop.org
> https://www.redhat.com/mailman/listinfo/message-bus-list
--