From: Christian Kujau <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: oom with 2.6.11
Date: Thu, 17 Mar 2005 03:00:16 +0100 [thread overview]
Message-ID: <4238E4B0.40703@g-house.de> (raw)
In-Reply-To: <20050316175109.3c160d4d.akpm@osdl.org>
Andrew Morton wrote:
>
> Some application went berzerk, used up all the swap and then oomed the box.
>
> You could perhaps run `top -d1' then hit M so the output is sorted by
> bloatiness, then try to catch the culprit.
i've already done that. as OOM happens when i am not around, i did that
with "ps":
http://lkml.org/lkml/2005/3/12/88
http://nerdbynature.de/bits/sheep/2.6.11/oom/daily_stats-2.6.11-rc5-bk2.log.gz
> But it would be better to have some app which prints the N most
> memory-hungry processes every second and simply scrolls that up the screen.
> I'm not aware of such a thing, but it could be cooked up via
> /proc/N/cmdline and /proc/N/statm.
i hope the link above does reveal this information.
i just wrote a bug report for the (debian), ppp package, but to know
*where* the memory goes to would really help, i think.
thank you,
Christian.
--
BOFH excuse #72:
Satan did it
next prev parent reply other threads:[~2005-03-17 2:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 15:21 oom with 2.6.11 Christian Kujau
2005-03-09 13:18 ` Mauricio Lin
2005-03-09 13:41 ` Mauricio Lin
2005-03-09 14:00 ` Christian Kujau
2005-03-10 15:12 ` Christian Kujau
2005-03-11 0:39 ` Andrew Morton
2005-03-11 1:14 ` Christian Kujau
2005-03-11 7:45 ` Pasi Kärkkäinen
2005-03-11 9:01 ` Mauricio Lin
2005-03-11 15:09 ` Christian Kujau
2005-03-15 8:52 ` Mauricio Lin
2005-03-15 14:12 ` Christian Kujau
2005-03-20 14:35 ` [SOLVED] " Christian Kujau
2005-03-11 10:59 ` Coywolf Qi Hunt
2005-03-11 15:10 ` Christian Kujau
2005-03-12 18:06 ` Christian Kujau
2005-03-17 1:27 ` Christian Kujau
2005-03-17 1:51 ` Andrew Morton
2005-03-17 2:00 ` Christian Kujau [this message]
2005-03-17 21:25 ` Coywolf Qi Hunt
2005-03-18 1:59 ` Christian Kujau
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 13:22 OOM " Christian Kujau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4238E4B0.40703@g-house.de \
--to=evil@g-house.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox