Description of problem: In several occasions, the script may end with return code 0 even when the service does not start correctly. For example [ -x /usr/sbin/vsftpd ] || exit 0 Version-Release number of selected component (if applicable): all How reproducible: always Steps to Reproduce: 1. change access rights such that /usr/sbin/vsftpd is not executable 2. service vsftpd start 3. echo $? Actual results: 0 Expected results: Non-zero exit code with respect to our guidelines. 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 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.
Fix checked in CVS and the new packages were built successfully. This issue should be resolved in vsftpd-2.0.1-6.el4
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2008-0680.html
this fix seems to have broken sites with multiple config files. the init script line 31 should be changed to read: [ -z "$CONFS" ] && exit 6 without the quotes, it generates an error from test about binary operator expected. should a new bug be opened?