Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 21
    Your comment is a useful warning, but instead of taking a ranting tone, it would have been far more useful to have quoted the fd_set(3) man page and that the limit comes from FD_SETSIZE. And the best would have been a suggestion of a replacement call like poll(3), as in this answer Commented Nov 26, 2019 at 19:48
  • this rant doesn't seem to have anything to do with the difference between the ulimit limits and file-max in /proc, nor do we know the software mentioned uses select() or is affected by its limitations. Commented May 13, 2022 at 12:59
  • 1
    Really enlightening, until reading this I would have used select as I was taught in college (~20 years ago). Commented Mar 27, 2023 at 22:58
  • 1
    Dude. Lighten up. Raging against the machine is fine, but why rage against your grandmother's machine? The first paragraph of the select(2) man page says " All modern applications should instead use poll(2) or epoll(7)". Commented Apr 23, 2023 at 23:27
  • 1
    Thanks @O. Jones, but "nfortunately many libraries still use select and you see it used in all over example codes and tutorials" is still true. I guess it will be harder to bury "select" then it is to eliminate "gets" Commented Apr 25, 2023 at 7:41