Bug 90065 - missing manpage for ipcalc(3)
Summary: missing manpage for ipcalc(3)
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-05-01 21:37 UTC by Scott R. Godin
Modified: 2014-03-17 02:36 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2003-05-01 23:02:39 UTC


Attachments (Terms of Use)

Description Scott R. Godin 2003-05-01 21:37:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
in (man ipcalc) at the bottom it mentions 
SEE ALSO
        ipcalc(3)
and yet 
$man 3 ipcalc
gives: 
No entry for ipcalc in section 3 of the manual

*sigh* 

As I scan the list of bugs for 'initscripts' I see 179 bugs listed, NOT ONE OF
WHICH IS MARKED "CLOSED" .. they are all either NEW or ASSIGNED,  with a few
REOPENED for fun. That's just depressing. 

oh and 

$ ls /usr/share/doc/initscripts-6.95/
ChangeLog  changes.ipv6  ipv6-6to4.howto  ipv6-tunnel.howto  static-routes-ipv6
 sysconfig.txt  sysvinitfiles

evidently ipcalc(3) isn't in /usr/share/doc/* either. 




Version-Release number of selected component (if applicable):
$ rpm -qf `where ipcalc`
initscripts-6.95-1


How reproducible:
Always

Steps to Reproduce:
1. read ipcalc manpage, observe see also ipcalc(3)
2. attempt to read ipcalc(3) for additional info
3. fall flat on face even after also trying man -a ipcalc
    

Actual Results:  No entry for ipcalc in section 3 of the manual

Expected Results:  additional info? examples of proper usage of ipcalc?
Conversely, no "see also" section ? 

Additional info:

section 3 seems an odd place for the ipcalc "see also"

Comment 1 Bill Nottingham 2003-05-01 23:02:39 UTC
The default query doesn't show closed bugs.

Reference to ipcalc(3) removed... there is no library with that API.

Will be fixed in 7.19-1.


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