Description of problem: If the file /usr/bin/sesame is not executable, the command 'service sesame {action}' does not print out any error message and returns exit code 0. [root@lzhaldyb-rhel62i ~]# chmod 0444 /usr/bin/sesame [root@lzhaldyb-rhel62i ~]# ls -l /usr/bin/sesame -r--r--r--. 1 sesame sesame 77572 Nov 29 00:05 /usr/bin/sesame [root@lzhaldyb-rhel62i ~]# service sesame status [root@lzhaldyb-rhel62i ~]# echo $? 0 [root@lzhaldyb-rhel62i ~]# service sesame start [root@lzhaldyb-rhel62i ~]# echo $? 0 [root@lzhaldyb-rhel62i ~]# service sesame stop [root@lzhaldyb-rhel62i ~]# echo $? 0 Version-Release number of selected component (if applicable): sesame-1.0-2.el6.i686 How reproducible: always Steps to Reproduce: 1. Remove executable right from /usr/bin/sesame: chmod 0444 /usr/bin/sesame 2. Run init script: service sesame {action} Actual results: No error message, exit code 0. Expected results: Error message stating that sesame is not executable, exit code different from 0. Additional info:
There is one more problem with sesame init script: it does not print anything if the {action} is wrong: [root@lzhaldyb-rhel62i ~]# service sesame dance [root@lzhaldyb-rhel62i ~]# echo $? 0 The usage message should be printed in this case listing all supported actions. Also, the exit code in this case should differ from 0.
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.