[SOLVED] Minor bug in BLFS dbus installation

Keith Hedger · 03-05-2013, 07:00 AM

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

But in the bootscript from blfs-bootscripts-20120828/blfs/init.d the pidfile/socket is set like so

Code:

pidfile=/run/dbus/pid
socket=/run/dbus/system_bus_socket

This prevents dbus from starting ( and so ConsoleKit and maybe others ).

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.

stoat · 03-05-2013, 08:00 AM

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.

Keith Hedger · 03-05-2013, 08:47 AM

Quote:

Originally Posted by stoat

.../var/run is a symlink to /run...

Is this normal? I have a number of virtual machines installed and also a bootable Slackware and none of them have the symlink you describe nor have I seen it in the (C)(B)LFS books ( unless I missed a bit! ), and yes it would fix the problem as long as /var was not a separate partition or was mounted before dbus was run.

stoat · 03-05-2013, 09:43 AM

Well, it's normal for LFS anyway. That symlink is created by commands in section 6.5 of the v7.3 book.

Keith Hedger · 03-05-2013, 10:00 AM

Quote:

Originally Posted by stoat

Well, it's normal for LFS anyway. That symlink is created by commands in section 6.5 of the v7.3 book.

Hmmm... just checked my script which builds the file system hierarchy and the command to make the link is there but definitely no link it must have been over written somewhere, I guess its not a big deal to have it either way, don't have clue where it got overwritten though.
I'll mark as solved.