public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Forking shell bombs
Date: Tue, 8 Jul 2003 17:51:37 -0500	[thread overview]
Message-ID: <20030708225137.GA1031@dbz.icequake.net> (raw)
In-Reply-To: <3F0B2CE6.8060805@nni.com>


On an Athlon 600 running 2.4.20, with ulimit -u 2047, the box recovers
no problem from the fork bomb.

On my Celeron 800 running 2.4.21, ulimit -u 1500, the box recovers after
4-5 minutes.

ulimit -u 2047 (Debian's default ulimit), the box fights for 5-10
minutes, and no longer responds after 10.  I can see fork perrors in
the terminal like usual, but the machine no longer responds. (I waited
more than half an hour.)

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

  parent reply	other threads:[~2003-07-08 22:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030708193401.24226.95499.Mailman@lists.us.dell.com>
2003-07-08 20:28 ` Forking shell bombs 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
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 [this message]
2003-07-10 12:32     ` Luiz Capitulino
2003-07-08 23:05   ` Wakko Warner
2003-07-09 11:36   ` Michael Buesch
2003-07-09 11:05 Arvind Kandhare
  -- strict thread matches above, loose matches on Subject: below --
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=20030708225137.GA1031@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --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