Bug 485801 - RFE - make service cmirror status report something
Summary: RFE - make service cmirror status report something
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: cmirror
Version: 4
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Chris Feist
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-16 20:20 UTC by Corey Marthaler
Modified: 2010-01-12 02:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-18 21:08:18 UTC
Embargoed:


Attachments (Terms of Use)
new init script (2.14 KB, text/plain)
2009-02-25 20:15 UTC, Jonathan Earl Brassow
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1043 0 normal SHIPPED_LIVE cmirror bug-fix update 2009-05-18 21:08:16 UTC

Description Corey Marthaler 2009-02-16 20:20:04 UTC
Description of problem:
This is the RHEL4 version of bug 460229.

I would be nice if the init script could report if the mod was loaded and clogd
was started like other scripts.


[root@hayes-03 cluster]# service cmirror status
[root@hayes-03 cluster]# echo $?
1


  status)
        rtrn=1
        ;;

  *)



Version-Release number of selected component (if applicable):
cmirror-1.0.1-1

Comment 1 Jonathan Earl Brassow 2009-02-25 20:15:35 UTC
Created attachment 333216 [details]
new init script

new init script that can be put in CVS build repo.

Comment 2 Jonathan Earl Brassow 2009-02-25 20:18:32 UTC
feist, you want to handle pulling the init script into the build repository?

Comment 3 Chris Feist 2009-02-25 23:19:54 UTC
Buidling into cmirror-1.0.2-1.el4

Comment 6 errata-xmlrpc 2009-05-18 21:08:18 UTC
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 therefore 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-2009-1043.html


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