2.6.23.8: OOM killer kills wrong jobs

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: LKML <linux-kernel@...>
Date: Friday, December 7, 2007 - 5:25 am

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
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
2.6.23.8: OOM killer kills wrong jobs, Martin MOKREJŠ, (Fri Dec 7, 5:25 am)
Re: 2.6.23.8: OOM killer kills wrong jobs, Alan Cox, (Fri Dec 7, 10:44 am)