Status command of init script should return appropriate exit code

We are noticing that chef doesn't always start, enable, or restart the service on CentOS 6.5. It turned out this was due to do one of the three init scripts missing an exit with a non-zero return code under the status() section.