From 1b9b90d94aac489e85517cc5ee69d075b1f3bc6b Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sun, 9 Apr 2017 23:09:50 +0200 Subject: libcurl-thread.3: also mention threaded-resolver Reported-by: Alex Bligh Bug: https://curl.haxx.se/mail/lib-2017-04/0044.html --- docs/libcurl/libcurl-thread.3 | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/libcurl/libcurl-thread.3 b/docs/libcurl/libcurl-thread.3 index 379ca8ffa..f520da3b7 100644 --- a/docs/libcurl/libcurl-thread.3 +++ b/docs/libcurl/libcurl-thread.3 @@ -5,7 +5,7 @@ .\" * | (__| |_| | _ <| |___ .\" * \___|\___/|_| \_\_____| .\" * -.\" * Copyright (C) 2015 - 2016, Daniel Stenberg, , et al. +.\" * Copyright (C) 2015 - 2017, Daniel Stenberg, , et al. .\" * .\" * This software is licensed as described in the file COPYING, which .\" * you should have received as part of this distribution. The terms @@ -77,9 +77,10 @@ without using either the c-ares or threaded resolver backends. When using multiple threads you should set the \fICURLOPT_NOSIGNAL(3)\fP option to 1L for all handles. Everything will or might work fine except that timeouts are not honored during the DNS lookup - which you can work around by building libcurl -with c-ares support. c-ares is a library that provides asynchronous name -resolves. On some platforms, libcurl simply will not function properly -multi-threaded unless this option is set. +with c-ares or threaded-resolver support. c-ares is a library that provides +asynchronous name resolves. On some platforms, libcurl simply will not +function properly multi-threaded unless the \fICURLOPT_NOSIGNAL(3)\f option is +set. .IP "Name resolving" \fBgethostby* functions and other system calls.\fP These functions, provided by your operating system, must be thread safe. It is very important that -- cgit v1.2.3