Simon McVittie <s...@debian.org> writes: > On Thu, 06 Jun 2024 at 18:39:15 +0200, Marco d'Itri wrote:
>> 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>. I took a quick look at the old INN source and didn't see anything obvious. I was half-expecting it to do something like set the soft limit to the hard limit (that sounds like a very INN sort of thing to do), but if so, I couldn't find it in a quick search. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
