Boost C++ Libraries: Ticket #5124: EMFILE handling https://svn.boost.org/trac10/ticket/5124 <p> What is the recommended way to handle EMFILE on accept? The chat server example returns from the handler without doing a new accept, which means the server won't accept any new connections after hitting EMFILE. This is undesirable. I've just been bitten by this myself. </p> <p> Would it be possible for Asio itself to handle this situation gracefully? </p> <p> <a class="ext-link" href="http://think-async.com/Asio/boost_asio_1_4_7/doc/html/boost_asio/example/chat/chat_server.cpp"><span class="icon">​</span>http://think-async.com/Asio/boost_asio_1_4_7/doc/html/boost_asio/example/chat/chat_server.cpp</a> </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/5124 Trac 1.4.3 anonymous Thu, 27 Jan 2011 11:33:32 GMT component changed; owner set https://svn.boost.org/trac10/ticket/5124#comment:1 https://svn.boost.org/trac10/ticket/5124#comment:1 <ul> <li><strong>owner</strong> set to <span class="trac-author">chris_kohlhoff</span> </li> <li><strong>component</strong> <span class="trac-field-old">None</span> → <span class="trac-field-new">asio</span> </li> </ul> Ticket chris_kohlhoff Mon, 06 Jun 2011 01:53:48 GMT status changed; resolution set https://svn.boost.org/trac10/ticket/5124#comment:2 https://svn.boost.org/trac10/ticket/5124#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> As of release branch <a class="changeset" href="https://svn.boost.org/trac10/changeset/72428" title="Merge asio from trunk.">[72428]</a>, examples have been updated to treat accept failures as non-fatal. </p> Ticket Olaf van der Spek <olafvdspek@…> Mon, 06 Jun 2011 11:35:22 GMT <link>https://svn.boost.org/trac10/ticket/5124#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/5124#comment:3</guid> <description> <p> Thanks. You might also want to use boost::make_shared instead of new. </p> </description> <category>Ticket</category> </item> </channel> </rss>