-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
process.ulimit #2009
Comments
Also #1941 |
@jorangreef ship sailed a while ago and magical ulimit bumping is now in core. won't change anytime soon. ulimits are not directly translatable to win32 so I am hesitant to add this to core. |
I personally would find it handy if node just had builtin a complete binding to all unix system calls, but I don't think that is really feasible, and the fact that its not portable to win32 is definitely a strike against it. Also, definitely fails the "can it be practically done outside of node" test: I agree, this can be done as an addon, and has been: https://www.npmjs.com/search?q=getrlimit -1 |
Closing since this doesn't translate to all platforms, and is available as a npm module. |
It would be great if there was a way for users to change ulimit explicitly from within a io.js/node.js process.
Something like process.setulimit and process.getulimit.
For users who don't understand EMFILE, it would make it easier for them to increase the limit especially on OS X without having to use an interim bash script calling ulimit before launching their script.
It would also avoid having node do something magical like reset the ulimit in the background, and it would expose more of the os capabilities to the user, which is always great.
The text was updated successfully, but these errors were encountered: