Re: [patch] resolv.conf.5: Timeout does not map to resolver API calls.
From: Florian Weimer <hidden>
Date: 2016-12-05 16:31:40
On 12/05/2016 05:09 PM, Carlos O'Donell wrote:
quoted hunk
diff --git a/man5/resolv.conf.5 b/man5/resolv.conf.5 index 553f093..241565d 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
Looks reasonable to me. Thanks, Florian -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html