Re: reached select() limit

2017-01-25 Thread David Guillen Fandos
Ha! Sorry for that, I just realized that it returns a bitmap of sockets. Why doesn't it return something like uint32_t? Allright then, so there's really no way to workaround my problem except, perhaps, to initialize c-ares at the begining of the process. But c-ares doesn't guarantee that all

Re: reached select() limit

2017-01-25 Thread Daniel Stenberg
On Wed, 25 Jan 2017, David Guillen Fandos wrote: Yeah agreed, but how do you retrieve the fds to use poll? With getsock you get up to 16 sockets which is insufficient for my needs (and also, BTW, sounds like an arbitrary and ridiculous number to hardcode in such a function) Arbitrary? Not re

Re: reached select() limit

2017-01-25 Thread Brad House via c-ares
Why is 16 too few? Do you have more than 8-16 name servers configured? Remember, it is one fd per nameserver (or possibly 2 if it has to fall back to TCP), NOT one fd per query, as my original reply stated. The ares_getsock is what you'd use, and yes, it does have a limit of 16 fds. -Brad On 1

Re: reached select() limit

2017-01-25 Thread David Guillen Fandos
Yeah agreed, but how do you retrieve the fds to use poll? With getsock you get up to 16 sockets which is insufficient for my needs (and also, BTW, sounds like an arbitrary and ridiculous number to hardcode in such a function) Thanks! On 25/01/17 04:05, Zan Lynx wrote: That will not help bec