Minor bug in BLFS dbus installation
Just found a small but annoying bug when installing dbus from here:
http://www.linuxfromscratch.org/blfs...eral/dbus.html The useradd command is: Code:
useradd -c "D-Bus Message Daemon User" -d /var/run/dbus -u 18 -g messagebus -s /bin/false messagebus Code:
pidfile=/run/dbus/pid So either the boot script must be changed or the adduser command, either way is easy but may trip up some first timers. I found it easier to set the pidfile/socket location in the init file to "/var/run/dbus" rather than change the user. |
I can't comment about ConsoleKit (and maybe others) since I don't install it. But on my current system that I built back in September from svn-2012-09-02 and blfs-bootscripts-20120828 with dbus-1.6.4, the situation was the same as you reported today. Same useradd command. Same pidfile and socket definitions in the dbus script. The daemon seems to start and run okay for me. My next system, which I'm now building from svn-2013-03-02 and blfs-bootscripts-20130212 with dbus-1.6.8, also does not seem to have a dbus problem. In both systems, /var/run is a symlink to /run. I would not have predicted a problem from those differences in the messagebus user home dir and the dbus init script. Maybe so though, sometimes. Maybe people who create a separate partition for /var would notice something.
|
Quote:
|
Well, it's normal for LFS anyway. That symlink is created by commands in section 6.5 of the v7.3 book.
|
Quote:
I'll mark as solved. |
All times are GMT -5. The time now is 06:54 AM. |