[zeromq-dev] defining behavior for running out of FDs
pelletier.michel at gmail.com
Sun Sep 30 20:56:37 CEST 2012
Here's a PR from what I think is the correct changeset from libxs:
I'm don't know why ENOBUFS was removed from the ipc_listener.cpp and
replaced with ENFILE. In the tcp case it was retained. Martin, was
there a reason for that or should the ENOBUFS case remain?
On Fri, Sep 28, 2012 at 2:27 AM, Pieter Hintjens <pieterh at gmail.com> wrote:
> Thanks for the heads up. Sounds like a good idea.
> On Sep 28, 2012 9:05 AM, "Martin Sustrik" <sustrik at 250bpm.com> wrote:
>> On 28/09/12 02:09, MinRK wrote:
>> > I'm not sure where all of the FD requests are, but one is inbound
>> > connections. Is it possible/sensible to simply reject new connections
>> > if FD allocation fails?
>> > If anyone more familiar with the core can enumerate all of the FD
>> > allocations, then perhaps we can see if it's possible to have defined
>> > failures, rather than unrecoverable crashes.
>> The "out of FDs" problem was already solved in XS , feel free to
>> backport it to 0MQ in case of need.
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
More information about the zeromq-dev