mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: dean-list-linux-kernel@arctic.org (dean gaudet)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	andihartmann@freenet.de (Andreas Hartmann),
	linux-kernel@vger.kernel.org (Kernel-Mailingliste)
Subject: Re: [2.4.18] Security: Process-Killer if machine get's out of memory
Date: Tue, 26 Mar 2002 23:47:04 +0000 (GMT)	[thread overview]
Message-ID: <E16q0ee-0004Dx-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.33.0203261210540.26944-100000@twinlark.arctic.org> from "dean gaudet" at Mar 26, 2002 12:24:58 PM

> what's the point if you're just going to get signal delivery when you
> least want it, even when malloc returns non-NULL?  it could even be due to

If you are running with no overcommit you'll always (for any statistically
interesting case get the malloc NULL and no signals)

> it's guaranteed to work in all cases.  (hence, apache-1.3 and other
> multiprocess daemon superiority over threaded and event-driven code, tee
> hee :)

thttpd -> 1000 hits/second on a 32Mb pentium

I don't hear you 8)


      reply	other threads:[~2002-03-26 23:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-24 12:09 andreas
     [not found] ` <3C9DC6D0.3080606@wanadoo.fr>
2002-03-24 13:24   ` Andreas Hartmann
     [not found]     ` <3C9DD653.8090701@wanadoo.fr>
2002-03-24 13:36       ` Andreas Hartmann
2002-03-24 13:30 ` Rik van Riel
2002-03-24 14:08   ` Andreas Hartmann
2002-03-24 16:54     ` Alan Cox
2002-03-24 16:59       ` Andreas Hartmann
     [not found]     ` <3C9E48B8.9080707@ngforever.de>
2002-03-24 22:23       ` Andreas Hartmann
2002-03-24 15:58 ` Chris Swiedler
2002-03-24 16:57 ` Alan Cox
2002-03-24 16:59   ` Roy Sigurd Karlsbakk
2002-03-24 17:45     ` Rik van Riel
2002-03-24 17:57       ` Christian Bornträger
2002-03-24 18:01         ` Rik van Riel
2002-03-24 18:03         ` Bernd Petrovitsch
2002-03-24 18:23         ` Alan Cox
2002-03-24 18:37         ` Andreas Hartmann
2002-03-24 18:20     ` Alan Cox
2002-03-24 19:20     ` Itai Nahshon
2002-03-24 17:24   ` Andreas Hartmann
2002-03-24 18:22     ` Alan Cox
2002-03-24 18:23       ` Mr. James W. Laferriere
2002-03-24 19:49         ` Alan Cox
2002-03-24 19:48           ` Mr. James W. Laferriere
2002-03-24 20:39             ` Alan Cox
2002-03-24 18:32       ` Andreas Hartmann
2002-03-24 19:50         ` Alan Cox
2002-03-24 20:43           ` Paul P Komkoff Jr
2002-03-25 15:09           ` Rok Papež
2002-03-26 20:24           ` dean gaudet
2002-03-26 23:47             ` Alan Cox [this message]

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=E16q0ee-0004Dx-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=andihartmann@freenet.de \
    --cc=dean-list-linux-kernel@arctic.org \
    --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

all inboxes | Powered by JetHome®