Hi, first of all, sorry for not being up to date with how the OOM killer works. I think there used to be a kernel config option to disable OOM killer and instead kill the process which actually asks for the memory and supposedly caused the memory lack. That is what I would like to have on my system. I a have a 1GB RAM laptop and use t-coffee software from http://www.tcoffee.org/Projects_home_page/t_coffee_home_page.html to do some science. ;) # grep Killed /tmp/dmesg.killed.txt Killed process 5733 (seamonkey-bin) Killed process 10011 (t_coffee) Killed process 5647 (FvwmPager) Killed process 5659 (xterm) # Killing just t_coffee would have been enough. $ perl -e 'print ">one\n"; print "ATGCCGTAAATGCATG"x100000; print "\n>two"; print "GGGGCCCCAT"x1000; print "\n"' > testcase.txt $ t_coffee testcase.txt ... [you should run out of memory soon] So, how can I change the behaviour or kernel? Please Cc: me in replies. Thanks. Martin
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Andy Whitcroft | clam |
| Ingo Molnar | [patch] paravirt: VDSO page is essential |
git: | |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Lovich, Vitali | RE: [PATCH] Packet socket: mmapped IO: PACKET_TX_RING |
| David Miller | [GIT]: Networking |
