Description of problem: Some constructions in netfs, network and single initscripts violate our initscript guidelines. Main problems are incorrect error codes and exiting the script without calling status command when it is supposed to. For example of such construction, look at these: [ -f /etc/sysconfig/network ] || exit 0 [ "${NETWORKING}" = "no" ] && exit 0 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.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Changing this would change the behavior of initscripts in a update release, which is bad form. Also, not having the network configured isn't really an error; this script is sort of a special case.