Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 25 Sep 2002 14:59:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 25 Sep 2002 14:59:37 -0400 Received: from 2-225.ctame701-1.telepar.net.br ([200.193.160.225]:21635 "EHLO 2-225.ctame701-1.telepar.net.br") by vger.kernel.org with ESMTP id ; Wed, 25 Sep 2002 14:59:37 -0400 Date: Wed, 25 Sep 2002 16:04:15 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Mark Mielke cc: Mark Veltzer , Peter Svensson , Linux kernel mailing list Subject: Re: Offtopic: (was Re: [ANNOUNCE] Native POSIX Thread Library 0.1) In-Reply-To: <20020925145727.B14820@mark.mielke.cc> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1000 Lines: 32 On Wed, 25 Sep 2002, Mark Mielke wrote: > I missed this one. Does this mean that fork() bombs will have limited > effect on root? :-) Indeed. A user can easily run 100 while(1) {} loops, but to the other users in the system it'll feel just like 1 loop... > I definately want this, even on my home machine. I've always found it > to be a sort of fatal flaw that per-user resource scheduling did not > exist on the platforms of my choice. It has existed since 2.2.14 or so ;) I just didn't get around to forward-porting it to newer 2.4 kernels, until last weekend. cheers, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ Spamtraps of the month: september@surriel.com trac@trac.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/