Andrew Benton wrote: > On Fri, 16 Dec 2011 20:27:29 +0000 > Ken Moffat <[email protected]> wrote: > >> Ah, I see, you build dbus but not the bootscripts. AFAIK, the >> bootscript has been required for a long time. I see no obvious >> reason to add dbus-launch to .xinitrc. > > I also see no reason to add dbus-launch to .xinitrc. On my system I > start dbus with a bootscript, I can see it in ps aux as: > dbus-daemon --system
> but I also see: > dbus-launch --autolaunch 465105239381aefc38f1f5e20000020d --binary-syntax > --close-stderr > and: > /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session > so it seems that something that uses it (notification-daemon?) uses > dbus-launch to spawn another dbus-daemon for the session even though > there is one running for the system. I don't think the system one is > needed. I'm not an expert in how dbus is used, but if you do not use the bootscript and do use the dbus-launch, isn't that sufficient? What I'd like to do is explain it, but I need to understand it better first. I think this is a mechanism for different processes to communicate without using shared memory or semaphores or pipes, but it may just be a wrapper around those constructs. I suspect (but am not sure) that dbus is not very useful on a non-gui desktop or server. If that's the case, then launching via dbus-launch to .xinitrc makes sense. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
