On Sat, Jul 20, 2013 at 4:52 PM, Adrian Chadd <adr...@creative.net.au> wrote: > On 20 July 2013 10:50, Oleg Moskalenko <mom040...@gmail.com> 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. best wishes, -- Nick *********************************************************************** To unsubscribe, send an e-mail to majord...@freehaven.net with unsubscribe libevent-users in the body.
