Differences between version 2 and revision by previous author of ENFILE.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Saturday, February 28, 2004 5:43:36 pm | by CraigBox | Revert |
| Older page: | version 1 | Last edited on Monday, October 28, 2002 9:56:33 pm | by PerryLorier | Revert |
@@ -3,5 +3,5 @@
The system has reached the maximum number of files it will allow to be open at once system wide.
This is usually caused by a runaway process or group of processes. For example a cron job that runs a program but that program never exiting will eventually either run the system out of memory, out of processes, or out of files.
-lsof(1
), fuser(1) etc can be used to try and determine what is using the files and killing the offending processes. Also, you can up the system wide number of files by putting a larger number into /proc/sys/fs/file-max, you will probably have to update /proc/sys/fs/inode-max too (maximum number of open inodes).
+lsof(8
), fuser(1) etc can be used to try and determine what is using the files and killing the offending processes. Also, you can up the system wide number of files by putting a larger number into /proc/sys/fs/file-max, you will probably have to update /proc/sys/fs/inode-max too (maximum number of open inodes). See ProcessNotes
.
