Hacker News new | past | comments | ask | show | jobs | submit login

Then 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



It's not just memory, it's cleanup that the Kernel must perform when the process terminates.


So? 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.


Don't leak things with limits.


It's not a "leak" if you're actually using it, you know.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: