From: "Riley Williams" <Riley@Williams.Name>
To: "David Ford" <david+powerix@blue-labs.org>,
"Ryan Underwood" <nemesis-lists@icequake.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Forking shell bombs
Date: Sun, 13 Jul 2003 10:10:22 +0100 [thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAOELCENAA.Riley@Williams.Name> (raw)
In-Reply-To: <3F0C2FCB.8060304@blue-labs.org>
Hi all.
It sounds like what is required is some way of basically saying
"Don't permit new processes to be created if CPU usage > 75%"
(where the 75% is configurable but less than 100%).
Best wishes from Riley.
---
* Nothing as pretty as a smile, nothing as ugly as a frown.
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of David Ford
> Sent: Wednesday, July 09, 2003 4:08 PM
> To: Ryan Underwood
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Forking shell bombs
>
> No such thing exists. I can have 10,000 processes doing nothing and
> have a load average of 0.00. I can have 100 processes each sucking cpu
> as fast as the electrons flow and have a dead box.
>
> Learn how to manage resource limits and you can tuck another feather
> into your fledgeling sysadmin hat ;)
>
> david
>
> Ryan Underwood wrote:
>
>> Hi,
>>
>> On Tue, Jul 08, 2003 at 04:43:18PM -0400, jhigdon wrote:
>>
>>> Have you tried this on any 2.5.x kernels? Just curious to see what it
>>> does, I plan on giving it a go later.
>>
>> I haven't, but a previous poster indicated that they had (2.5.74) with
>> the same results.
>>
>> I wonder if we could find an upper limit on the number of allowable
>> processes that would leave the box in a workable state? Unfortunately,
>> I don't have a spare box to test such things on at the moment. ;)
>>
>> Thanks,
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.500 / Virus Database: 298 - Release Date: 10-Jul-2003
next prev parent reply other threads:[~2003-07-13 8:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 20:28 Ryan Underwood
2003-07-08 20:37 ` vlad
2003-07-08 20:43 ` jhigdon
2003-07-08 21:25 ` Ryan Underwood
2003-07-08 22:43 ` Sir Ace
2003-07-09 15:07 ` David Ford
2003-07-09 21:10 ` Ryan Underwood
2003-07-13 9:10 ` Riley Williams [this message]
2003-07-13 9:40 ` Jan-Benedict Glaw
2003-07-13 14:17 ` Gene Heskett
2003-07-08 21:59 ` system_lists
2003-07-08 17:18 ` Max Valdez
2003-07-08 22:25 ` Alan Cox
2003-07-08 22:26 ` Svein Ove Aas
2003-07-08 22:51 ` Ryan Underwood
2003-07-10 12:32 ` Luiz Capitulino
2003-07-08 23:05 ` Wakko Warner
2003-07-09 11:36 ` Michael Buesch
-- strict thread matches above, loose matches on Subject: below --
2003-07-09 11:05 Arvind Kandhare
2003-07-08 22:26 Perez-Gonzalez, Inaky
2003-07-08 18:45 Ryan Underwood
2003-07-08 18:55 ` Charles Cazabon
2003-07-08 22:01 ` Alan Cox
2003-07-08 19:23 ` jhigdon
2003-07-08 20:35 ` vlad
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=BKEGKPICNAKILKJKMHCAOELCENAA.Riley@Williams.Name \
--to=riley@williams.name \
--cc=david+powerix@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nemesis-lists@icequake.net \
/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
all inboxes | Powered by JetHome®