alex lupu wrote: > 1. The Makefile doesn't seem to have an "uninstall-dbus" entry.
An oversight. > 2. For some reason, the 'pid' and 'system_bus_socket' files are > created in '/var/run/dbus/' and not in '/run/dbus' as one would > expect by examining the dbus script. > The '/run/dbus' directory _is_ created at boot-up time but ends up empty. /var/run should be a symlink to /run so /run/dbus is created and is equivanet to /var/run/dbus. > 3. I made a couple of _temporary_ changes in my 'dbus' script. > In "start)" section: > > 3.1. Just before 'start_daemon ...', I inserted > 'rm -f /var/run/dbus/pid' > > This is so that I can avoid the ugly message on my system boot-up: > "Starting the D-Bus Messagebus Daemon...Failed to start message bus: > The pid file "/var/run/dbus/pid" exists, if the message bus is not running, > remove this file" If you have the symlink /run will always be empty at boot. > 3.2. Just before ';;', I inserted > 'chown alex:users /var/run/dbus/system_bus_socket' > I know this one is sheer heresy, but I needed it for a quick and dirty > test of the latest "Chrome" browser (134477) which works now but still > looks for a "/var/run/dbus/system_bus_socket": > "ERROR: Failed to connect to socket /var/run/dbus/system_bus_socket" > (Chrome is very unhappy if run from anything other than a > non-privileged account.) Your rules. :) > Until I figure out a way to start 'dbus-daemon' from a user login > cleanly in order to quiet down Chrome, the 3.2. work-around will have to do. > Thanks for the suggestions in BLFS "D-BUS-1.4.20" but I've failed to > find a stable and satisfactory solution so far. Check the symlink and then see if you still have the problems. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
