3 ms·
It's not that it's a proxy for memory use, but FD is its own resource, I've seen many software with FD leak (i.e. they open a file and forget about it, if they
by gnulinux 1y ago
It's not that it's a proxy for memory use, but FD is its own resource, I've seen many software with FD leak (i.e. they open a file and forget about it, if they need the file again, they open another FD) so this limit can be a method to tell that it's leaking. Whether that's a good idea/necessary depends on the application.
- quotemstr 1y agoThen account for _kernel memory used_ by file descriptors and account it like any other ulimit. Don't impose a cap on file descriptors in particular. These caps distort program design throughout the ecosystem
- Dwedit 1y agoIt's not just memory, it's cleanup that the Kernel must perform when the process terminates.
- quotemstr 1y agoSo? Doesn't matter. Account for the thing you want to control directly. Don't put caps on bad proxies for the thing you want to control.
- tedunangst 1y agoDon't leak things with limits.
- quotemstr 1y agoIt's not a "leak" if you're actually using it, you know.