You can use lsof to understand who's opening so many files. Usually it's a (web) server that opens so many files, but lsof will surely help you ...
- 2 - Check the limits of a running process. - 3 - Tracking a possible file descriptors leak. - 4 - Tracking open files in real time. - 5 - Specific to DB2.
SocketException: too many files open is a tricky error to solve, as many
Tested and works on Ubuntu 9.04 and 10.04. Note: Editing
By default, the maximum number of files that Mac OS X can open is set to 12,288 and
Too many files open fatal error with Guzzle
Even so, most apps will find that they have more memory headroom on
**Stalls here until ^C is entered** ***] ^C[*] Shutting down payload stager listener. ... What I think might be the relevant stack trace is below:
Many of our docs examples have been updated to use cy.intercept() in place of cy.route()
echo sysctl kern.openfiles