#5124 closed Bugs (fixed)
EMFILE handling
| Reported by: | Owned by: | chris_kohlhoff | |
|---|---|---|---|
| Milestone: | Boost 1.47.0 | Component: | asio |
| Version: | Boost 1.45.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
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.
Would it be possible for Asio itself to handle this situation gracefully?
http://think-async.com/Asio/boost_asio_1_4_7/doc/html/boost_asio/example/chat/chat_server.cpp
Change History (3)
comment:1 by , 12 years ago
| Component: | None → asio |
|---|---|
| Owner: | set to |
comment:2 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
As of release branch [72428], examples have been updated to treat accept failures as non-fatal.