From: Daniel Stenberg Date: Thu, 4 Nov 2010 08:49:02 +0000 (+0100) Subject: CURLOPT_NOSIGNAL: add blurb about SIGPIPE X-Git-Tag: curl-7_21_3~112 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d95b67f4092c5f35ea615aba085b44ce9ae92243;p=curl CURLOPT_NOSIGNAL: add blurb about SIGPIPE --- diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index cfd7d30a8..ea2630d6e 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -84,6 +84,13 @@ If this option is set and libcurl has been built with the standard name resolver, timeouts will not occur while the name resolve takes place. Consider building libcurl with c-ares support to enable asynchronous DNS lookups, which enables nice timeouts for name resolves without signals. + +Setting \fICURLOPT_NOSIGNAL\fP to 1 makes libcurl NOT ask the system to ignore +SIGPIPE signals, which otherwise are sent by the system when trying to send +data to a socket which is closed in the other end. libcurl makes an effort to +never cause such SIGPIPEs to trigger, but some operating systems have no way +to avoid them and even on those that have there are some corner cases when +they may still happen, contrary to our desire. .IP CURLOPT_WILDCARDMATCH Set this option to 1 if you want to transfer multiple files according to a file name pattern. The pattern can be specified as part of the