Description of problem: sqlgrey init script 'status' command returns wrong exit code. It doesn't play well with other scripts which are rely on exit codes. For example puppet can't restart sqlgrey if service is down. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. stop sqlgrey service 2. Run 'service sqlgrey status' Actual results: Exit code is '0' sqlgrey is stopped [alex@alex /home/alex]$ echo $? 0 Expected results: Exit code shouldn't be 0 if service Additional info: Proposal patch: --- sqlgrey.orig 2016-07-19 20:14:18.071907619 +0000 +++ sqlgrey 2016-07-19 20:13:44.919988132 +0000 @@ -47,6 +47,7 @@ status) status sqlgrey + RETVAL=$? ;; reload)
sqlgrey-1.7.6-4.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-7b86273834
sqlgrey-1.7.6-4.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-7b86273834
sqlgrey-1.7.6-4.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.