Description of problem: If the networking is down, the script ends with error code 0 even though the service is not started. The reason is: [ "${NETWORKING}" = "no" ] && exit 0 Also the error code for unimplemented feature of the script is not correct, it should be 3 instead of one at the end of the script. Version-Release number of selected component (if applicable): all How reproducible: always Steps to Reproduce: 1. service network stop 2. service dhcdbd start/status 3. echo $? Actual results: 0 Expected results: correct non-zero error code/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.
Created attachment 205951 [details] dhcdbd-2.2-initscript.patch
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. This request will be reviewed for a future Red Hat Enterprise Linux release.
dhcdbd is obsoleted by the NetworkManager rebase in RHEL 5.3. Further, dhcdbd won't be present in RHEL 6.0. Given the low impact of this bug, I'm just going to close it because I see no reason to tie up QA resources to update the init script (and we haven't seen any interest from PM or QA to get this bug fixed up in 5.1 through 5.3, so I see no reason to keep it open).