mirror of
https://github.com/moparisthebest/curl
synced 2024-08-13 17:03:50 -04:00
Mention more restrictions on timeouts when using signals
This commit is contained in:
parent
f0bb9c7d8d
commit
9c86097286
@ -21,7 +21,7 @@
|
|||||||
.\" * $Id$
|
.\" * $Id$
|
||||||
.\" **************************************************************************
|
.\" **************************************************************************
|
||||||
.\"
|
.\"
|
||||||
.TH curl_easy_setopt 3 "16 Oct 2008" "libcurl 7.19.1" "libcurl Manual"
|
.TH curl_easy_setopt 3 "28 Oct 2008" "libcurl 7.19.1" "libcurl Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
curl_easy_setopt \- set options for a curl easy handle
|
curl_easy_setopt \- set options for a curl easy handle
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
@ -81,8 +81,10 @@ process. This option is mainly here to allow multi-threaded unix applications
|
|||||||
to still set/use all timeout options etc, without risking getting signals.
|
to still set/use all timeout options etc, without risking getting signals.
|
||||||
(Added in 7.10)
|
(Added in 7.10)
|
||||||
|
|
||||||
|
If this option is set and libcurl has been built with the standard name
|
||||||
|
resolver, timeouts will not occur while the name resolve takes place.
|
||||||
Consider building libcurl with ares support to enable asynchronous DNS
|
Consider building libcurl with ares support to enable asynchronous DNS
|
||||||
lookups. It enables nice timeouts for name resolves without signals.
|
lookups, which enables nice timeouts for name resolves without signals.
|
||||||
.PP
|
.PP
|
||||||
.SH CALLBACK OPTIONS
|
.SH CALLBACK OPTIONS
|
||||||
.IP CURLOPT_WRITEFUNCTION
|
.IP CURLOPT_WRITEFUNCTION
|
||||||
@ -1300,8 +1302,10 @@ In unix-like systems, this might cause signals to be used unless
|
|||||||
\fICURLOPT_NOSIGNAL\fP is set.
|
\fICURLOPT_NOSIGNAL\fP is set.
|
||||||
.IP CURLOPT_TIMEOUT_MS
|
.IP CURLOPT_TIMEOUT_MS
|
||||||
Like \fICURLOPT_TIMEOUT\fP but takes number of milliseconds instead. If
|
Like \fICURLOPT_TIMEOUT\fP but takes number of milliseconds instead. If
|
||||||
libcurl is built to use the standard system name resolver, that part will
|
libcurl is built to use the standard system name resolver, that portion
|
||||||
still use full-second resolution for timeouts. (Added in 7.16.2)
|
of the transfer will still use full-second resolution for timeouts with
|
||||||
|
a minimum timeout allowed of one second.
|
||||||
|
(Added in 7.16.2)
|
||||||
.IP CURLOPT_LOW_SPEED_LIMIT
|
.IP CURLOPT_LOW_SPEED_LIMIT
|
||||||
Pass a long as parameter. It contains the transfer speed in bytes per second
|
Pass a long as parameter. It contains the transfer speed in bytes per second
|
||||||
that the transfer should be below during \fICURLOPT_LOW_SPEED_TIME\fP seconds
|
that the transfer should be below during \fICURLOPT_LOW_SPEED_TIME\fP seconds
|
||||||
@ -1364,9 +1368,11 @@ timeouts). See also the \fICURLOPT_TIMEOUT\fP option.
|
|||||||
In unix-like systems, this might cause signals to be used unless
|
In unix-like systems, this might cause signals to be used unless
|
||||||
\fICURLOPT_NOSIGNAL\fP is set.
|
\fICURLOPT_NOSIGNAL\fP is set.
|
||||||
.IP CURLOPT_CONNECTTIMEOUT_MS
|
.IP CURLOPT_CONNECTTIMEOUT_MS
|
||||||
Like \fICURLOPT_CONNECTTIMEOUT\fP but takes number of milliseconds instead. If
|
Like \fICURLOPT_CONNECTTIMEOUT\fP but takes the number of milliseconds
|
||||||
libcurl is built to use the standard system name resolver, that part will
|
instead. If libcurl is built to use the standard system name resolver,
|
||||||
still use full-second resolution for timeouts. (Added in 7.16.2)
|
that portion of the connect will still use full-second resolution for
|
||||||
|
timeouts with a minimum timeout allowed of one second.
|
||||||
|
(Added in 7.16.2)
|
||||||
.IP CURLOPT_IPRESOLVE
|
.IP CURLOPT_IPRESOLVE
|
||||||
Allows an application to select what kind of IP addresses to use when
|
Allows an application to select what kind of IP addresses to use when
|
||||||
resolving host names. This is only interesting when using host names that
|
resolving host names. This is only interesting when using host names that
|
||||||
|
Loading…
Reference in New Issue
Block a user