Re: Running with vm.overcommit_memory=2

[Stan Bubrouski <stan ccs neu edu>]

Ralf Ertzinger wrote:
<SNIP>
> A bug report against what? I do not think this is the kernels fault.
> The kernel I tried on was 2.6.10-1.1143_FC4

I wouldn't make the assumption that its not the kernel, seems like its 
the kernel for sure?  For instance:

sh: fork: Cannot allocate memory
sh: fork: Cannot allocate memory

This is not a good sign when you have free memory, but on the surface 
this does indeed to be a kernel problem... who you think decides there 
is no memory? :)

-sb