Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 25 Sep 2002 15:12:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 25 Sep 2002 15:12:44 -0400 Received: from line106-15.adsl.actcom.co.il ([192.117.106.15]:53395 "EHLO www.veltzer.org") by vger.kernel.org with ESMTP id ; Wed, 25 Sep 2002 15:12:43 -0400 Message-Id: <200209251929.g8PJTPN05751@www.veltzer.org> Content-Type: text/plain; charset=US-ASCII From: Mark Veltzer Organization: Meta Ltd. To: Rik van Riel , Mark Mielke , Linux kernel mailing list , Peter Svensson Subject: Re: Offtopic: (was Re: [ANNOUNCE] Native POSIX Thread Library 0.1) Date: Wed, 25 Sep 2002 22:29:22 +0300 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1179 Lines: 34 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 25 September 2002 22:04, you wrote: > 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... Rik! This is terrific!!! How come something like this was not merged in earlier ?!? This seems like an absolute neccesity!!! I'm willing to test it if that is what is needed to get it merged. What does Linus and others feel about this and most importantly when will see it in ? (Hopefully in this development cycle). Regards, Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9kg6SxlxDIcceXTgRApApAKClB60zgDs0OB1ltb2ha0Lo8cescgCfTVE7 ZiNKbiTAN78LecVGt6/JzPU= =/z0y -----END PGP SIGNATURE----- - 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/