On Saturday 14 June 2003 16:38, Andrew Dunstan wrote: > IOW, simply the presence of /proc/sys/vm/overcommit_memory with a value set > to 0 doesn't guarantee you won't get an OOM kill, AFAICS.
Right. You need the value to be 2 or 3. Which means you need Alan's patch to do that. > I *know* the latest RH kernel docs *say* they have paranoid mode that > supposedly guarantees against OOM - it was me that pointed that out > originally :-). I just checked on the latest sources (today it's RH8, > kernel 2.4.20-18.8) to be doubly sure, and can't see the patches. (That > would be really bad of RH, btw, if I'm correct - saying in your docs you > support something that you don't) But note these two lines in the docs with 2.4.20-13.9 (RHL9 errata): * This describes the overcommit management facility in the latest kernel tree (FIXME: actually it also describes the stuff that isnt yet done) Pay double attention to the line that says FIXME. IOW, they've documented stuff that might not be done! You can try Red Hat's enterprise kernel, but you'll have to build it from source. RHEL AS is available online as source RPMs. Also understand that the official Red Hat kernel is very close to an Alan Cox kernel. Also, if you really want to get down and dirty testing the kernel, a test suite is available to help with that, known as Cerberus. Configs are available specifically tuned to stress-test kernels. I think Cerberus is on Source Forge. So, make sure you have a kernel that allows overcommit-accounting mode 2 to prevent kills on OOM. Theoretically mode 2 will prevent the possiblity of OOM completely. If I read things right, if you have double swap space mode 0 will not OOM nearly as quickly. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11 ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend