libcURL behavior with unexpected socket close
Date: Sun, 12 Apr 2009 17:00:10 +0200
I'm a newbie as libcURL user.
I was wondering how curl behaves in some scenarios under Linux.
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.
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?
Thanks in advance,
Received on 2009-04-12