Bug 187298

Summary: `service ccsd status` returns 0 when ccsd is NOT running (should return non 0)
Product: [Retired] Red Hat Cluster Suite Reporter: Stanko Kupcevic <kupcevic>
Component: ccsAssignee: Abhijith Das <adas>
Status: CLOSED CURRENTRELEASE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: 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: 2010-01-27 18:14:31 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:
Description Flags
This should
none
This should fix the problem
none
This should fix the problem none

Description Stanko Kupcevic 2006-03-29 20:29:00 UTC
Description of problem:
`/etc/init.d/ccsd start` returns 1 when ccsd is running (should return 0).
`/etc/init.d/ccsd status` returns 0 when ccsd is NOT running (0 s/b for
"service OK" only).

This causes problems for conga, when it determines cluster status and
starts/stops a node. 

Both 'start' and 'status' deviate from behavior of other init scripts, and so is
a bug. 


Version-Release number of selected component (if applicable):
ccs-1.0.0-0

How reproducible:
Always

Comment 1 Abhijith Das 2006-03-30 23:09:12 UTC
Created attachment 127082 [details]
This should

Comment 2 Abhijith Das 2006-03-30 23:09:40 UTC
Created attachment 127083 [details]
This should fix the problem

Comment 3 Abhijith Das 2006-03-31 21:43:09 UTC
Created attachment 127161 [details]
This should fix the problem

Comment 4 Abhijith Das 2006-04-10 18:39:37 UTC
committed above patch into CVS; RHEL4, STABLE and HEAD branches