Red Hat Bugzilla – Bug 717770
Need single-request-reopen option documented for resolv.conf
Last modified: 2012-09-12 05:46:12 EDT
Description of problem:
More of your users are going to be using this option as more deploys of RHEL 6 go out. See here for they why: http://www.linuxquestions.org/questions/showthread.php?p=4399340#post4399340
This option is not currently documented and it needs to be.
Version-Release number of selected component (if applicable):
man resolv.conf look for single-request-open
I have filed an upstream bug here: https://bugzilla.kernel.org/show_bug.cgi?id=38542
This issue also effect Fedora 15, and probably rawhide too.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
Created attachment 524346 [details]
This has been taken from the KCS article attached to the case.
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.
Unless I am missing something here, even after updating to RHEL 6.2 I cannot see this in the man page, I can see another overlay the EDNS0 options but not the single-request-open option.
I see this sub-paragraph in "man 5 resolv.conf" under options:
single-request-reopen (since glibc 2.9)
The resolver uses the same socket for the A and AAAA
requests. Some hardware mistakenly only sends back one
reply. When that happens the client sytem will sit and
wait for the second reply. Turning this option on
changes this behavior so that if two requests from the
same port are not handled correctly it will close the
socket and open a new one before sending the second
Hmm pretty clearly I am doing somehting wrong. Looked on multiple 6.2 systems after the update and was unable to see that paragraph. Glad though that other people can.
manpath was bad, this works just fine, sorry for all the noise.
I see that option documented on a Red Hat Enterprise Linux Server release 6.3 (Santiago) system, which claims at the bottom of the man page: "This page is part of release 3.22 of the Linux man-pages project."
However, it isn't in the Fedora-17 resolv.conf man page, which claims: "This page is part of release 3.35 of the Linux man-pages project."
Nor is it in the git HEAD at the man-pages project.
I'm not sure what the process is for moving fixes across projects, but something has slipped throught the cracks here that could be better. Just sayin'.
Thanks for the notice Todd. I'll fix this in Fedora. (And thanks for submitting this to upstream). I am going to review man-pages bugs in RHEL and fix them in Fedora, it looks like there are more bugs like this one..