Re: Setting oom_adj on linux?

Alex Hunsaker <badalex@gmail.com>

From: Alex Hunsaker <badalex@gmail.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Magnus Hagander <magnus@hagander.net>, Alvaro Herrera <alvherre@commandprompt.com>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-01-08T19:30:44Z
Lists: pgsql-hackers
On Fri, Jan 8, 2010 at 10:24, Stephen Frost <sfrost@snowman.net> wrote:
> As I recall, oom_adj wasn't visible in the container because you
> explicitly set what proc entries processes can have access to when using
> VServers, and OpenSSH didn't handle that cleanly.  Guess what I'm just
> saying is "don't just assume everything is as it would be on a 'normal'
> system when dealing with /proc and friends", and, of course, test, test,
> test when you're talking about back-porting things.

Sure this was openssh? I just looked through the entire cvs history
for opensshp and found 0 references to 'oom' let alone 'oom_adj'.
Maybe something distro specific?


[ for the curious here is what I tried ]
$ git clone git://git.infradead.org/openssh.git
$ cd openssh
$ git grep oom_adj
$ git grep 'oom'
$ git grep oom | grep -vi loomis | grep -v room
$ git log -p | grep oom | grep -vi loomis | grep -v room | grep -v tsoome