Commit 6273b23a authored by Daniel Stenberg's avatar Daniel Stenberg
Browse files

FAQ: expand the thread-safe section

... with a mention of *NOSIGNAL, based on talk in bug #1386
parent 1cef8f0b
Loading
Loading
Loading
Loading
+6 −0
Original line number Original line Diff line number Diff line
@@ -1099,6 +1099,12 @@ FAQ
  your system has such.  Note that you must never share the same handle in
  your system has such.  Note that you must never share the same handle in
  multiple threads.
  multiple threads.


  libcurl's implementation of timeouts might use signals (depending on what it
  was built to use for name resolving), and signal handling is generally not
  thread-safe.  Multi-threaded Applicationss that call libcurl from different
  threads (on different handles) might want to use CURLOPT_NOSIGNAL, e.g.:

    curl_easy_setopt(handle, CURLOPT_NOSIGNAL, true);


  If you use a OpenSSL-powered libcurl in a multi-threaded environment, you
  If you use a OpenSSL-powered libcurl in a multi-threaded environment, you
  need to provide one or two locking functions:
  need to provide one or two locking functions: