Bug 134995 - clumanager init script should have default case, error non-zero
clumanager init script should have default case, error non-zero
Status: CLOSED ERRATA
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: clumanager (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-10-07 16:01 EDT by Derek Anderson
Modified: 2009-04-16 16:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-02-28 15:31:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Fixes problem as well as upgrade problem when no /etc/cluster.xml is present (697 bytes, patch)
2004-12-16 13:41 EST, Lon Hohberger
no flags Details | Diff

  None (edit)
Description Derek Anderson 2004-10-07 16:01:37 EDT
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:
Comment 1 Lon Hohberger 2004-10-08 10:00:15 EDT
You're right, it should.
Comment 2 Lon Hohberger 2004-12-16 13:41:44 EST
Created attachment 108734 [details]
Fixes problem as well as upgrade problem when no /etc/cluster.xml is present
Comment 4 Derek Anderson 2005-02-28 15:31:41 EST
Verified against clumanager-1.2.25-2.  Scheduled for release RHEL3-U5.
Comment 5 Jay Turner 2005-05-25 12:41:00 EDT
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

Note You need to log in before you can comment on or make changes to this bug.