diff options
| author | Carlos O'Donell <carlos@redhat.com> | 2016-12-05 11:09:54 -0500 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2016-12-06 11:40:16 +0100 |
| commit | dd9454a65486b5c95ad9d8cc5907b700d4cb1af6 (patch) | |
| tree | 44c7f644587b06580b84e04efbe5d68a0fa9bbc3 /man5 | |
| parent | f5f41651053d5bd9e0d693a968aa49f33f6c46a6 (diff) | |
| download | man-pages-dd9454a65486b5c95ad9d8cc5907b700d4cb1af6.tar.gz | |
resolv.conf.5: Timeout does not map to resolver API calls
I'm posting this patch to clarify the timeout behaviour because
there have been developers who expect this timeout to mean
something it is not.
The timeout (and by proxy attempts) does not map to resolver API
calls. For example a single call to getent might involve multiple
resolution requests to the resolvers listed in resolv.conf and
each request will use TIMEOUT and be attempted at least ATTEMPT
times. A developer using the resolver API cannot easily compute
any given timeout because the implementation may change e.g. A and
AAAA queries made in parallel. A system administrator uses this
setting to ensure there is a desirable timeout on any request to
any of the nameservers listed in resolv.conf, but no guarantees
exist beyond that.
Reviewed-by: Florian Weimer <fweimer@redhat.com>
Signed-off-by: Carlos O'Donell <carlos@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man5')
| -rw-r--r-- | man5/resolv.conf.5 | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/man5/resolv.conf.5 b/man5/resolv.conf.5 index 553f0939ec..241565da83 100644 --- a/man5/resolv.conf.5 +++ b/man5/resolv.conf.5 @@ -161,7 +161,10 @@ The value for this option is silently capped to 15. .\" Since glibc 2.2 Sets the amount of time the resolver will wait for a response from a remote name server before retrying the -query via a different name server. +query via a different name server. This may +.BR not +be the total time taken by any resolver API call and there is no +guarantee that a single resolver API call maps to a single timeout. Measured in seconds, the default is .BR RES_TIMEOUT |