Re: [Libevent-users] Re: libevent2 stuck in Linux, CPU 100%

[Nick Mathewson <nickm@xxxxxxxxxxxxx>]

On Wed, Jul 31, 2013 at 10:40 PM, Nick Mathewson <nickm@xxxxxxxxxxxxx> wrote:
> On Sat, Jul 20, 2013 at 4:52 PM, Adrian Chadd <adrian@xxxxxxxxxxxxxxx> wrote:
>> On 20 July 2013 10:50, Oleg Moskalenko <mom040267@xxxxxxxxx> wrote:
>   [...]
>>> By the way, I have, to some extend, a similar situation with TCP sockets.
>>> When I have a listening socket, and the number of socket exceeds the system
>>> limit, then I am getting messages from the listening libevent callback like:
>>>
>>> [warn] Error from accept() call: Too many open files
>>>
>>> Basically, the system just has to wait till the socket number decreases.
>>> Reporting million errors to the stderr at this moment, from my point of
>>> view, rather pointless. Understandably, accept() has problems in the too
>>> many open files condition, but I am not sure that it has to be reported to
>>> stderr so many times.
>>
>> Same deal here. It'd be nice to represent this in an OS-agnostic way
>> so you don't end up with everyone just using EV_READ on accept
>> sockets, and then having to special case everything. :(
>
> I've opened https://github.com/libevent/libevent/issues/71 for this;
> insight welcome.

On that ticket, Nir and I have realized that there's already
(apparently) a good workaround; please have a look over there and let
us know if we're missing something important?

best wishes,
-- 
Nick
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.