All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Mauricio Lin <mauriciolin@gmail.com>,
	elenstev@mesatop.com, coywolf@gmail.com,
	Andrew Morton <akpm@osdl.org>
Subject: [SOLVED] Re: oom with 2.6.11
Date: Sun, 20 Mar 2005 15:35:41 +0100	[thread overview]
Message-ID: <423D8A3D.9090602@g-house.de> (raw)
In-Reply-To: <4236ED5F.9020301@g-house.de>

for the record: the "oom bug" turned out to be user generated. a *lot* of
small scripts were started, triggering oom again and again, user error.

the source of the problem is still pppd and the discussion continues as a
debian bugreport:

    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299875

thank you for all your help,
Christian.
-- 
BOFH excuse #139:

UBNC (user brain not connected)

  reply	other threads:[~2005-03-20 14:35 UTC|newest]

Thread overview: 21+ 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                 ` Christian Kujau [this message]
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
2005-03-17 21:25         ` Coywolf Qi Hunt
2005-03-18  1:59           ` 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=423D8A3D.9090602@g-house.de \
    --to=evil@g-house.de \
    --cc=akpm@osdl.org \
    --cc=coywolf@gmail.com \
    --cc=elenstev@mesatop.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mauriciolin@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.