resolver.3, resolv.conf.5: RES_DEBUG is only available if glibc is compiled with debug support

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692136
and https://bugzilla.kernel.org/show_bug.cgi?id=43061

Reported-by: Nathan Stratton Treadway <kernelbugs@nathanst.com>
Reported-by: Simon Heimberg <simohe@besonet.ch>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2013-03-05 08:06:31 +01:00
parent e2b6e497a2
commit 7d63c0a424
2 changed files with 7 additions and 1 deletions

View File

@ -186,6 +186,10 @@ has been called.
.TP
.B RES_DEBUG
Print debugging messages.
This option is only available if glibc was built with debugging enabled,
.\" See resolv/README.
.\" Support for RES_DEBUG was made conditional in glibc 2.2.
which is not the default.
.TP
.B RES_AAONLY
Accept authoritative answers only.

View File

@ -133,7 +133,9 @@ where \fIoption\fP is one of the following:
sets
.BR RES_DEBUG
in
.IR _res.options .
.IR _res.options
(only effective if glibc was built with debug support; see
.BR resolver (3)).
.TP
.BI ndots: n
.\" Since glibc 2.2