> I somehow managed to get the above message when doing something *extremely*
> intensive in raw sockets. What exactly does this mean and how do I fix it?
You seem to have hit the system-wide inode maximum... I don't know why :)
To see how many you have used, do this:
cat /proc/sys/kernel/inode-nr
To check what your system-wide limit is:
cat /proc/sys/kernel/inode-max
If inode-nr == inode-max, then this is indeed your problem.
To increase your system-wide maximum:
echo "32768" > /proc/sys/kernel/inode-max
(You will have to add this to your rc files if you want it to work across
reboots - this doesn't write anything to your kernel)
Note that 32768 is probably waay to much...
Oskar
--- "Haven't slept at all. I don't see why people insist on sleeping. You feel so much better if you don't. And how can anyone want to lose a minute - a single minute of being alive?" -- Think Twice- 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/