From: Alvaro Figueroa <fede2@fuerzag.ulatina.ac.cr>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.4.18 and strange OOM Killer behaveness
Date: 27 Apr 2002 08:29:15 -0600 [thread overview]
Message-ID: <1019917755.7548.6.camel@lucy> (raw)
In-Reply-To: <200204261636.14573.mcp@linux-systeme.de>
> So, you guess, apache, mysqld, squid and the causer pico are killed, but NO,
> ONLY, and i mean ONLY pico was killed, all the other Processes listed above
> are running fine, accepting connections, short: works fine!!
I'm probably talking nonsense here, but apache, mysql and squid; all of
them run there services with several processes. Could it be that the OOM
Killer only killed a couple of childs and not the parent of them all?
--
Alvaro Figueroa
next prev parent reply other threads:[~2002-04-27 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 14:38 Kernel 2.4.18 and strange OOM Killer behaveness Marc-Christian Petersen
2002-04-26 19:56 ` Diego Calleja
2002-04-27 14:29 ` Alvaro Figueroa [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-26 17:46 Dieter Nützel
2002-04-26 21:25 ` Andrea Arcangeli
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=1019917755.7548.6.camel@lucy \
--to=fede2@fuerzag.ulatina.ac.cr \
--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