James> Your printf's were like this
James> fprintf (stderr, "%u ", totalmalloc);
James> So it could fail somewhere between the first and last fprintf.
Actually I noticed that bug and fixed it right after sending the
email, the fprintfs now look like this:
fprintf (stderr, "M%u\n", totalmalloc);
since stderr gets flushed after every newline, I know that the program
is actually hanging in the malloc.
Me> My process is not being killed, because I have disabled the OOM
Me> killer. What I really want to do is set
Me> /proc/sys/vm/overcommit_memory to 2, but the problem with that is
Me> bash won't even execute normal programs, even though I have 32MB
Me> of ram!
James> You may also need to increase the amount of free memory the
James> kernel will try to hold.
Are you referring to the /proc/sys/vm/overcommit_ratio ?
I've tried setting it at 50%, 80%, 90%, and 100%, but bash still won't
fork programs for me.
Dave
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
