Messages in this thread | | | Date | Thu, 8 Oct 1998 09:38:07 +1000 | From | Matthew Hawkins <> | Subject | 2.1.124+ /proc/sys/fs/inode-max wrong? |
| |
G'day smiley happy people :)
I have this problem with 2.1.124, and both .125 pre-patches. It seems that a lot of programs are refusing to function as they complain about "too many open files" and so forth. Now I know this is rubbish as the same programs happen to function fine with 2.0.35, and 2.1.119. I can reproduce it with Debian's apt, Netscape Navigator 4.06, and XF86_S3.
Now what I think seems to be the problem is the default setting of /proc/sys/fs/inode-max. The documentation from Rik says that this setting should be 3-4 times greater than file-max. file-max is of course set to 4096 by default, and to my surprise, so is inode-max. Increasing inode-max to 16384 seems to get rid of the "too many open files" problem.
What's the story here?
-- Matt
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |