From 467309406e725a9756c6a8380582ed3684b90670 Mon Sep 17 00:00:00 2001 From: Jay Satiro Date: Wed, 29 Jul 2015 02:05:32 -0400 Subject: libcurl-thread.3: Clarify CURLOPT_NOSIGNAL takes long value 1L --- docs/libcurl/libcurl-thread.3 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/libcurl/libcurl-thread.3 b/docs/libcurl/libcurl-thread.3 index 070b47a2b..745ce474e 100644 --- a/docs/libcurl/libcurl-thread.3 +++ b/docs/libcurl/libcurl-thread.3 @@ -84,9 +84,9 @@ You may need to provide one or two functions to allow it to function properly: \fBSignals.\fP Signals are used for timing out name resolves (during DNS lookup) - when built without using either the c-ares or threaded resolver backends. When using multiple threads you should set the -\fICURLOPT_NOSIGNAL(3)\fP option to 1 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 +\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. -- cgit v1.2.3