Red Hat Bugzilla – Bug 187283
`service fenced status` returns 1 when fenced is running (should return 0)
Last modified: 2009-12-22 16:20:50 EST
Description of problem:
`/etc/init.d/fenced status` returns 1 when fenced is running (should return 0).
This causes problems for conga, when it determines cluster status and
starts/stops a node.
'status' deviates from behavior of other init scripts, and so is a bug.
Version-Release number of selected component (if applicable):
This is fixed in 4.4
Verified in fence-1.32.67-1.el4, but was probably fixed earlier.