Description of problem: According to https://fedoraproject.org/wiki/FCNewInit/Initscripts messagebus init script status should return exit code 2 if program is dead and /var/lock/subsys/messagebus file exists. Version-Release number of selected component (if applicable): dbus-1.2.16-5.fc12.x86_64 How reproducible: always Steps to Reproduce: 1. service messagebus stop 2. touch /var/lock/subsys/messagebus 3. service messagebus status; echo $? Actual results: exit code 3 - messagebus stopped Expected results: exit code 2 - messagebus dead but locked Additional info:
Do you have a patch ? The initscript looks fine to me ...
Stopping messagebus is not a supported operation.
Created attachment 361087 [details] messagebus initscript patch Attaching initscript patch. Seems like $servicename (messagebus) and $processname (dbus-daemon) was confused. Therefore lock files has wrong name (/var/lock/subsys/messagebus vs. /var/lock/subsys/dbus-daemon).
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I've committed this upstream: http://cgit.freedesktop.org/dbus/dbus/commit/?h=dbus-1.2&id=05283235632bc8891aaa3047563cb4a1edada033 And I will build into F-14. However note the entire concept of this enormous twisty copy&pasted shell script, lock files, pid files, etc. just to run a dbus-daemon process is totally wrong. We should be porting things to upstart, where the *ENTIRE* contents of the upstart script is just: exec /bin/dbus-daemon --nofork That's it. Really. (Actually for the system bus we want to get to the point where upstart starts it internally, but for other services, this is the right thing to do)
I should further elaborate on the concept of stopping the message bus. It would be possible to stop the bus safely if there are no active clients; for example if you're not running NetworkManager, avahi, don't have an X login session, etc. The current script just kills it arbitrarily disregarding client state, which has a high potential to break the running OS. If we wanted to support this, we could add a new interface to the system bus which atomically checks whether it's running, and if it isn't, terminates it. It might also be possible to have upstart grow launchd-like ability to spawn the bus the first time something connects to it.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.