Bug 916993

Summary: man-page is missing
Product: Red Hat Enterprise Linux 6 Reporter: Frank Danapfel <fdanapfe>
Component: pcsAssignee: Chris Feist <cfeist>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.4CC: amascari, cluster-maint, lnovich, rsteiger, slevine
Target Milestone: rcKeywords: Reopened
Target Release: 6.5   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: pcs-0.9.66-2.el6 Doc Type: Bug Fix
Doc Text:
Cause: Man page for pcs had not yet been created Consequence: Users were required to use --help instead of viewing a man page Fix: Man page for pcs was created. Result: Users can now view full documentation for pcs using the 'man pcs' command.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 11:51:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Frank Danapfel 2013-03-01 11:43:20 UTC
Description of problem:
The "pcs" package does not include a man-page

Version-Release number of selected component (if applicable):
pcs-0.9.26-11.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. man pcs
  
Actual results:
# more /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.4 Beta (Santiago)
# rpm -q pcs
pcs-0.9.26-11.el6.noarch
# man pcs
No manual entry for pcs

Expected results:
manual page should be available

Additional info:
It would also be nice if the man-page for pcs was available online somewhere (similar to http://www.nongnu.org/crmsh/crm.8.html)

Comment 3 RHEL Program Management 2013-03-07 20:55:23 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

Comment 9 Chris Feist 2013-08-13 23:39:14 UTC
[root@ask-02 pcs]# man pcs
... lots of output ...

Comment 12 errata-xmlrpc 2013-11-21 11:51:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1633.html