Re: Setting oom_adj on linux?
От | Alex Hunsaker |
---|---|
Тема | Re: Setting oom_adj on linux? |
Дата | |
Msg-id | 34d269d41001081130q4b8f4ac0v9139eb0f29e05a7c@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Setting oom_adj on linux? (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: Setting oom_adj on linux?
|
Список | 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
В списке pgsql-hackers по дате отправления: