I compiled loop-callo.c on my desktop machine. I ran it, and suddenly my firefox session was killed by OOM.
I don't understand why firefox was killed instead of the newly-created memory-eating process. Firefox was started much before loop-call was.
Is there anyother way to adjust OOM behaviour other than placing "OOM_DISABLE" on /proc/<pid>/oomadj ?
P.S : Good link -> http://linux-mm.org/OOM_Killer
© 2014, O’Reilly Media, Inc.
All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners.