All of lore.kernel.org
 help / color / mirror / Atom feed
From: Natanael Copa <mlists@tanael.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: "Jacek Łuczak" <difrost@pin.if.uz.zgora.pl>,
	linux-kernel@vger.kernel.org
Subject: Re: forkbombing Linux distributions
Date: Tue, 05 Apr 2005 11:47:09 +0200	[thread overview]
Message-ID: <1112694429.32468.27.camel@nc> (raw)
In-Reply-To: <1112289106.1829.10.camel@mindpipe>

On Thu, 2005-03-31 at 12:11 -0500, Lee Revell wrote:

> Didn't you ever look up what a ulimit is?

ofcourse i did. I just think that ulimit (or other userspace tools)
should be used to *raise* the limit if you need more. Not the reverse.

> If you consider your distro's default ulimits unreasonable, file a bug
> report with them.  But no one is going to make Linux "restrictive by
> default" to make life easier for people who don't bother to RTFM.

I already suggested ulimit solutions for my distro. They think that if
this is needed the kernel dev's would do something (ie its a kernel
problem) while the kernel dev's says this is a userspace prob.

I wouldn't bother if this was a problem for one or two distros only.
Now, almost all distros seems to be vulnerable by default.

I wouldn't bother if other *nixes would set this limit in userspace.
(the BSD's set the limit lower in kernel and let users who need more
raise with userland tools)

I wouldn't bother if this wouldn't give Linux a bad reputation.

I'm Sorry if I made some people upset.

--
Natanael Copa


  reply	other threads:[~2005-04-05  9:54 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 17:40 forkbombing Linux distributions Jacek Łuczak
2005-03-31 10:00 ` Natanael Copa
2005-03-31 17:11   ` Lee Revell
2005-04-05  9:47     ` Natanael Copa [this message]
2005-04-05 10:18       ` Jacek Luczak
  -- strict thread matches above, loose matches on Subject: below --
2005-03-28 17:28 Matthieu Castet
2005-03-28 17:56 ` folkert
2005-03-28 19:33   ` Jan Engelhardt
2005-03-28 19:39     ` folkert
2005-03-28 20:35       ` Renate Meijer
2005-03-29 12:31 ` Natanael Copa
2005-03-30 23:46 ` Felipe Alfaro Solana
2005-03-31  6:55   ` Natanael Copa
2005-03-31  7:09     ` Jacek Łuczak
2005-03-22 17:09 Natanael Copa
2005-03-21  3:06 William Beebe
2005-03-21  3:22 ` Dave Jones
2005-03-21  3:26   ` William Beebe
2005-03-21  3:27 ` Peter Chubb
2005-03-21  5:14   ` Grant Coady
2005-03-21  7:41     ` Jan Engelhardt
2005-03-22 11:26 ` Hikaru1
2005-03-22 11:49   ` Jan Engelhardt
     [not found]     ` <20050322124812.GB18256@roll>
2005-03-22 12:50       ` Hikaru1
2005-03-23 10:56         ` aq
2005-03-23 12:37           ` Natanael Copa
2005-03-23 13:04             ` aq
2005-03-23 13:38               ` Jan Engelhardt
2005-03-23 13:54               ` Natanael Copa
2005-03-23 14:20                 ` Måns Rullgård
2005-03-23 14:43                 ` Jan Engelhardt
2005-03-23 15:04                   ` Natanael Copa
2005-03-24  7:07                     ` Jan Engelhardt
2005-03-24 10:05                       ` Natanael Copa
2005-03-23 19:38                   ` Kyle Moffett
2005-03-23 20:26                     ` Natanael Copa
2005-03-23 17:05                 ` aq
2005-03-23 18:05                   ` Paul Jackson
2005-03-23 18:44                     ` aq
2005-03-23 20:15                       ` Natanael Copa
2005-03-23 20:48                   ` Natanael Copa
2005-03-23 13:45             ` Erik Mouw
2005-03-23 14:03               ` Natanael Copa
2005-03-23 13:53     ` Max Kellermann
2005-03-23 14:23       ` Natanael Copa
2005-03-23 14:27         ` Max Kellermann
2005-03-23 14:44           ` Natanael Copa
2005-03-23 14:52             ` Max Kellermann
2005-03-23 15:18               ` Natanael Copa
2005-03-26 10:37 ` Tux
2005-03-28  8:03   ` Natanael Copa

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=1112694429.32468.27.camel@nc \
    --to=mlists@tanael.org \
    --cc=difrost@pin.if.uz.zgora.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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.