Description of problem: If the /etc/quagga/bgpd.conf does not exist or the networking is shut down, then the script always ends with error code 0 (even if status is invoked). There are also wrong return codes in the script. Version-Release number of selected component (if applicable): all How reproducible: always Steps to Reproduce: 1. service network stop 2. service bgpd start/status... 3. echo $0 Actual results: 0 Expected results: non-zero exit code due to our guidelines or status of the service Additional info: When fixing this bug, please obbey our init script guidelines and be sure that status command is run correctly. Our guidelines are on following two pages: http://intranet.corp.redhat.com/ic/intranet/InitscriptsSpec.html http://intranet.corp.redhat.com/ic/intranet/InitscriptGuidelines.html For an example of the script that returns the error codes correctly and always runs status see: http://devserv.devel.redhat.com/~mmarcini/amd This bug is tracked by 237789.
*** This bug has been marked as a duplicate of 243143 ***
The inistcript is wrong but just FYI: service network stop doesn't affect value of NETWORKING variable in /etc/sysconfing/network so [ "${NETWORKING}" = "no" ] && exit 1 can pass even with network down.