Re: libcURL behavior with unexpected socket close
Date: Sun, 12 Apr 2009 23:54:01 +0200 (CEST)
On Fri, 10 Apr 2009, Marco Toldo wrote:
> If send() method of C sockets is invoked when either side closed connection,
> a SIGPIPE signal is sent to calling process, which by default terminates the
> process. A way to avoid this is to call send() with MSG_NOSIGNAL flag.
... right, if the OS/IP stack supports it.
> Does the CURLOPT_NOSIGNAL option of curl_easy_setopt() act the same for curl
> or something else is required in order to keep process alive?
libcurl attempts to disable SIGPIPE on its own as far as it can, so users of
libcurl should be able to simple ignore everything like that.
-- / daniel.haxx.seReceived on 2009-04-13