From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.4.2) Gecko/20040308 Description of problem: dbus init scripts do not honor stop or restart commands. For example, suppose I go into the /etc/dbus-1/system.conf file and make changes, I want them to take effect. So, its normal to do a: /etc/rc.d/init.d/messagebus restart command. However this fails. Version-Release number of selected component (if applicable): dbus-0.22-4 How reproducible: Always Steps to Reproduce: 1. /etc/rc.d/init.d/messagebus restart Actual Results: [root@buildhost root]# /etc/rc.d/init.d/messagebus status dbus-daemon-1 (pid 2448) is running... [root@buildhost root]# /etc/rc.d/init.d/messagebus restart Stopping system message bus: [FAILED] Starting system message bus: Failed to start message bus: The pid file "/var/run/dbus/pid" exists, if the message bus is not running, remove this file [FAILED] [root@buildhost root]# /etc/rc.d/init.d/messagebus stop Stopping system message bus: [FAILED] [root@buildhost root]# /etc/rc.d/init.d/messagebus status dbus-daemon-1 (pid 2448) is running... Expected Results: messagebus restarted successfully. Additional info:
Works for me. Did you perhaps install dbus from source at some point or are using a modified dbus spec? Please attach your /etc/dbus-1/system.conf file to this bug report.
OK. I found the problem. It turns out that during the configure script, it makes some decisions based on /etc/redhat-release being on a system. The build system did not have that file installed (since it wasn't required) and that's why the init scripts were not functioning correctly. So, the solution is to add: BuildRequires: /etc/redhat-release And that makes sure all decisions are correct.
Fixed in fc3-head
For some reason our build enviornments do not like redhat-release as BuildRequires. Adding a prebuilt init script until this is resolved.