Displaying 5 results from an estimated 5 matches for "curlopt_timeout".
2019 Sep 23
0
Re: [PATCH nbdkit v2] server: public: Add nbdkit_parse_* functions for safely parsing integers.
...t; static bool sslverify = true;
> -static long timeout = 0;
> +static uint32_t timeout = 0;
> @@ -334,7 +336,7 @@ curl_open (int readonly)
> curl_easy_setopt (h->c, CURLOPT_REDIR_PROTOCOLS, protocols);
> }
> if (timeout > 0)
> - curl_easy_setopt (h->c, CURLOPT_TIMEOUT, timeout);
> + curl_easy_setopt (h->c, CURLOPT_TIMEOUT, (long) timeout);
I might have left a comment here (the cast is necessary because
curl_easy_setopt() is varargs), so no one accidentally deletes the cast
thinking it is pointless.
> +++ b/plugins/ssh/ssh.c
> @@ -151,8 +152,11...
2010 Nov 23
0
[R] Catching a RCurl error?
...ing if this should be done in the level of tryCatch, or by
> playing with some parameter in the RCurl options)
>
>
> Thanks,
> Tal
That's a question that also popped up in my work. You can definitely tune
timeouts in the options (e.g. one options of interest in that respect is
CURLOPT_TIMEOUT, which I think is lowercase in the R implementation; there
are others, too; check http://curl.haxx.se/docs/manual.html and
http://curl.haxx.se/libcurl/c/libcurl-tutorial.html).
Generally there's a lot of stuff you can specify but I haven't found a way
yet to use some sort of an "inte...
2020 Nov 16
1
help with "too many clients awaiting authentication"
Hello guys,
Today we faced an unique problem.
We have about 120 stations and we are reaching 40k simultaneous listeners monday/friday (~ 11 AM GMT -3).
We also use url auth to log, audit and build audience reports.
But today, at the end of the day we were about 10k simultaneous and listeners start get errors (403, busy, please try again later), and after digging, delete logs and restart
2019 Sep 23
2
[PATCH nbdkit v2] server: public: Add nbdkit_parse_* functions for safely parsing integers.
...0) {
nbdkit_error ("'timeout' must be 0 or a positive timeout in seconds");
return -1;
}
@@ -334,7 +336,7 @@ curl_open (int readonly)
curl_easy_setopt (h->c, CURLOPT_REDIR_PROTOCOLS, protocols);
}
if (timeout > 0)
- curl_easy_setopt (h->c, CURLOPT_TIMEOUT, timeout);
+ curl_easy_setopt (h->c, CURLOPT_TIMEOUT, (long) timeout);
if (!sslverify) {
curl_easy_setopt (h->c, CURLOPT_SSL_VERIFYPEER, 0L);
curl_easy_setopt (h->c, CURLOPT_SSL_VERIFYHOST, 0L);
diff --git a/plugins/nbd/nbd-standalone.c b/plugins/nbd/nbd-standalone.c
index...
2019 Sep 23
2
Re: [PATCH nbdkit] server: public: Add nbdkit_parse_* functions for safely parsing integers.
On Mon, Sep 23, 2019 at 12:05:11PM -0500, Eric Blake wrote:
> > + int nbdkit_parse_long (const char *what, const char *str, long *r);
> > + int nbdkit_parse_unsigned_long (const char *what,
> > + const char *str, unsigned long *r);
>
> Do we really want to encourage the use of parse_long and
> parse_unsigned_long? Those differ between