Sponsored Content
Full Discussion: Unex
The Lounge War Stories Unex Post 302934324 by rbatte1 on Friday 6th of February 2015 07:24:48 AM
Old 02-06-2015
Nearest I get is gerp. I'm forever typing it. I don't know why.
This User Gave Thanks to rbatte1 For This Post:
 
CURLOPT_DNS_CACHE_TIMEOUT(3)				     curl_easy_setopt options				      CURLOPT_DNS_CACHE_TIMEOUT(3)

NAME
CURLOPT_DNS_CACHE_TIMEOUT - set life-time for DNS cache entries SYNOPSIS
#include <curl/curl.h> CURLcode curl_easy_setopt(CURL *handle, CURLOPT_DNS_CACHE_TIMEOUT, long age); DESCRIPTION
Pass a long, this sets the timeout in seconds. Name resolves will be kept in memory and used for this number of seconds. Set to zero to completely disable caching, or set to -1 to make the cached entries remain forever. By default, libcurl caches this info for 60 seconds. The name resolve functions of various libc implementations don't re-read name server information unless explicitly told so (for example, by calling res_init(3)). This may cause libcurl to keep using the older server even if DHCP has updated the server info, and this may look like a DNS cache issue to the casual libcurl-app user. Note that DNS entries have a "TTL" property but libcurl doesn't use that. This DNS cache timeout is entirely speculative that a name will resolve to the same address for a certain small amount of time into the future. DEFAULT
60 PROTOCOLS
All EXAMPLE
TODO AVAILABILITY
Always RETURN VALUE
Returns CURLE_OK SEE ALSO
CURLOPT_DNS_USE_GLOBAL_CACHE(3), CURLOPT_DNS_SERVERS(3), libcurl 7.54.0 February 03, 2016 CURLOPT_DNS_CACHE_TIMEOUT(3)
All times are GMT -4. The time now is 06:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy