Bug 813898 - No rpcbind entry in section 3 of the man pages as mentioned in rpcbind man page
No rpcbind entry in section 3 of the man pages as mentioned in rpcbind man page
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rpcbind (Show other bugs)
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Steve Dickson
Petr Beňas
: Documentation, FutureFeature, ManPageChange
Depends On:
  Show dependency treegraph
Reported: 2012-04-18 13:29 EDT by Nilesh Parmar
Modified: 2015-01-04 18:02 EST (History)
5 users (show)

See Also:
Fixed In Version: rpcbind-0.2.0-10.el6
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 02:55:22 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nilesh Parmar 2012-04-18 13:29:17 EDT
Description of problem:
No rpcbind entry in section 3 of the man pages as mentioned in rpcbind man page

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

How reproducible:
every time

Steps to Reproduce:
1. man rpcbind  
     rpcbind(3), ..."

2.man 3 rpcbind
No entry for rpcbind in section 3 of the manual
Actual results:
No Section 3 man page of rpcbind 

Expected results:
Section 3 man page of rpcbind to be displayed

Additional info: 
Also checked by downloading the tarball of rpcbind (http://www.linuxfromscratch.org/blfs/view/cvs/basicnet/rpcbind.html), but didnt found any section 3 man page for rpcbind.
Got the below files in man directory of tarball:-

Comment 3 Peter Schiffer 2012-07-20 08:04:17 EDT
rpcbind.8 man page is part of the rpcbind package - reassigning to the correct component
Comment 6 Petr Beňas 2012-08-29 10:06:32 EDT
Reproduced in rpcbind-0.2.0-9.el6.x86_64 and verified in rpcbind-0.2.0-10.el6.x86_64.
Comment 8 errata-xmlrpc 2013-02-21 02:55:22 EST
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.


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