Bug 479854 - missing man pages for thread-safe res_n* resolver functions
missing man pages for thread-safe res_n* resolver functions
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: man-pages (Show other bugs)
10
All Linux
low Severity medium
: ---
: ---
Assigned To: Ivana Varekova
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-13 11:40 EST by Jeff Bastian
Modified: 2009-04-21 03:02 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-04-21 03:02:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeff Bastian 2009-01-13 11:40:55 EST
Description of problem:
A man page exists for a number of resolver functions including res_init, res_query, res_search, etc, but not for the thread-safe 'res_n' flavor of those functions, res_ninit, res_nquery, res_nsearch, etc.

The thread-safe functions use a user-declared res_state struct instead of the shared _res. 

Please add man pages for res_ninit, res_nquery, res_nsearch, etc.


Version-Release number of selected component (if applicable):
man-pages-3.09-2.fc10
glibc-2.9-3

How reproducible:
every time

Steps to Reproduce:
1. man res_nquery
  
Actual results:
No manual entry for res_nquery

Expected results:
a man page on res_nquery should be displayed

Additional info:
In the glibc source tree, see resolv/README section "Using the resolver in multi-threaded code" for a description of the functions.

http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/libc/resolv/README?rev=1.2&cvsroot=glibc
Comment 1 Ivana Varekova 2009-04-21 03:02:04 EDT
This task is on man-pages upstream todo list now. If time permits I will  create the man page but there are probably more relevant persons (the authors of these functions) which could do it.

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