From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: "Nikita V. Youshchenko" <yoush@cs.msu.su>, linux-kernel@vger.kernel.org
Subject: Re: Local DoS (was: Strange 'zombie' problem both in 2.4 and 2.6)
Date: Mon, 14 Jun 2004 21:27:34 -0300 [thread overview]
Message-ID: <20040615002734.GA9801@logos.cnet> (raw)
In-Reply-To: <Pine.LNX.4.60.0406140959250.30433@dlang.diginsite.com>
On Mon, Jun 14, 2004 at 10:01:53AM -0700, David Lang wrote:
> I think I may be running into the same (or a similar) issue with a
> workload that forks heavily (~3500 forks/sec). What can I do to let the
> system survive this sort of load?
Hi David,
v2.6.7-mm tree contains a fix for this, adding a rlimit for
pending signals.
Can you describe the problem you are seeing in more detail?
next prev parent reply other threads:[~2004-06-15 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 9:11 Local DoS (was: Strange 'zombie' problem both in 2.4 and 2.6) Nikita V. Youshchenko
2004-04-09 14:45 ` Denis Vlasenko
2004-04-13 13:10 ` Marcelo Tosatti
2004-06-14 17:01 ` David Lang
2004-06-15 0:27 ` Marcelo Tosatti [this message]
2004-06-15 1:31 ` David Lang
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=20040615002734.GA9801@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yoush@cs.msu.su \
/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