|Summary:||Wrong init script|
|Product:||Red Hat Enterprise Linux 5||Reporter:||Michal Marciniszyn <mmarcini>|
|Component:||netlabel_tools||Assignee:||James Antill <james.antill>|
|Status:||CLOSED DEFERRED||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2007-06-06 13:04:20 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Michal Marciniszyn 2007-06-06 12:48:31 UTC
Description of problem: There is a bug in netlabel init script. The script returns correct error codes when invoked, however in some cases it may prevent correct call of status command of the script. The problem is in following lines, which in some rare cases end script too early: test `id -u` = 0 || exit 4 test -x /sbin/netlabelctl || exit 5 test -f $RULES || exit 6 The exit 4 case is probably correct, since in the case of insufficient rights, there might be need not to display the state of the service to the user, this IMHO depends on package specific consideration. The next two lines are not correct in any case. Version-Release number of selected component (if applicable): all How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: 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.
Comment 1 RHEL Product and Program Management 2007-06-06 13:04:20 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Since this bugzilla is in a component that is not approved for the current release, it has been closed with resolution deferred. You may reopen this bugzilla for consideration in the next release.