Bug 134995
| Summary: | clumanager init script should have default case, error non-zero | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Cluster Suite | Reporter: | Derek Anderson <danderso> | ||||
| Component: | clumanager | Assignee: | Lon Hohberger <lhh> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3 | CC: | cluster-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2005-02-28 20:31:41 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
You're right, it should. Created attachment 108734 [details]
Fixes problem as well as upgrade problem when no /etc/cluster.xml is present
Verified against clumanager-1.2.25-2. Scheduled for release RHEL3-U5. 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 the 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/RHBA-2005-047.html |
Description of problem: Just a nitpick enhancement. It seems to be standard practice in init scripts to have a default in the case selection in case some knob (like me) types 'service clumanager shutdown', gets a success error code and assumes his cluster has stopped. *) echo $"Usage: $0 {start|stop|status|restart}" exit 1 Version-Release number of selected component (if applicable): 1.2.16 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: