Bug 117749 - hosts_access(5) man page refers to missing man pages
Summary: hosts_access(5) man page refers to missing man pages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: tcp_wrappers
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Thomas Woerner
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-08 04:22 UTC by Landon Curt Noll
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-01 12:17:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Landon Curt Noll 2004-03-08 04:22:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624

Description of problem:
The hosts_access(5) man page says:

SEE ALSO
    ...
    tcpdchk(8), tcpdmatch(8), test programs.

There are no tcpdchk(8) or tcpdmatch(8) man pages.

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

How reproducible:
Always

Steps to Reproduce:
1.man 8 tcpdchk
2.man 8 tcpdmatch
3.
    

Actual Results:  Man pages not found.

Expected Results:  Either the hosts_access(5) man page would not refer
to these man pages
or these man pages would exist.

Additional info:

Are the test programs tcpdchk and tcpdmatch missing?  They are
nor installed with the tcp_wrappers-7.6-34 rpm.  Perhaps they
should be added?

Comment 1 Bastien Nocera 2004-11-16 17:15:08 UTC
tcpdchk and tcpdmatch only work with inetd, not xinetd, so they can't
be added...

Comment 2 Landon Curt Noll 2004-11-16 19:33:48 UTC
So then I recommend that the man page be changed to not refer to
tcpdchk and tcpdmatch.

Comment 3 Landon Curt Noll 2006-05-14 06:43:37 UTC
This is still the case for RHEL4.2

Comment 4 Landon Curt Noll 2006-07-29 08:25:29 UTC
This has been fixed in RHEL4.3.  This bug should now be closed.


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