On Thu, 06 Jun 2024 at 18:39:15 +0200, Marco d'Itri wrote: > On Jun 06, Simon McVittie <s...@debian.org> wrote: > > I believe the change Luca describes is increasing rlim_max (hard limit) > > but not rlim_cur (soft limit), and the code touched by that patch is > > looking at rlim_cur, so it should be unaffected anyway - unless some larger > > component is raising rlim_cur. > > Something did, because inn would start reporting ~1G available fds and > then explode, and that patch solved the issue. :-)
It might be worthwhile to try to track down what larger component did this, because inheriting a larger rlim_cur without opt-in can also break users of select(2) as described in <https://0pointer.net/blog/file-descriptor-limits.html>. smcv
