On Fri, 21 Feb 2003, Tom Reader wrote:

> I'm using libcurl for some HTTP GETs from a C program, and I am trying to
> use the CURLOPT_TIMEOUT and CURLOPT_CONNECTTIMEOUT parameters to control
> the length of the timeouts.

You're not using CURLOPT_NOSIGNAL, are you?

> With CURLOPT_CONNECTTIMEOUT, the parameter does affect the length of the
> timeout, but the values seem a little odd - the timeouts appear to be
> several times longer than I'd expect. Setting CURLOPT_CONNCETTIMEOUT to 30
> (which I'd expect to give a 30 second timeout) seems to give approximately
> a 5 minute timeout. Setting it to 2 gives something like a 15 second
> timeout, etc.

That sounds really odd. I can't say I've ever noticed that myself.

> While this means that I can get my timeouts roughly as I want them, I'm
> wondering if anyone else has this problem, and if there is a solution.
> Also, while I haven't tested it myself yet, I'm wondering whether the same
> thing applies to CURLOPT_TIMEOUT.

It's bound to be the same problems with TIMEOUT as that is basicly the same
thing, only stretched to apply to the whole transfer.

> Any help or comments would be appreciated.

Can you show us a nice repeatable way to see this problem? Can you
single-step through the debugger to see what things that are being used when
it should instead return?

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge