From owner-freebsd-current Fri Oct 29 6:58:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from megadodo.segNET.COM (megadodo.segNET.COM [206.34.181.3]) by hub.freebsd.org (Postfix) with ESMTP id 7948115626 for ; Fri, 29 Oct 1999 06:58:22 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc1a146.bf.sover.net [209.198.80.146]) by megadodo.segNET.COM (8.9.1a/8.8.5) with ESMTP id JAA16290; Fri, 29 Oct 1999 09:58:12 -0400 (EDT) Date: Fri, 29 Oct 1999 10:02:51 +0000 (GMT) From: Adam Strohl To: Luke Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: RE: protecting from attacks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to recall allowing a limit for max processes when I was looking at fork bombs back in '95 ... ahh the memories. - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - On Fri, 29 Oct 1999, Luke wrote: > I have been trying to figure out a sane method of stopping this one: > while(1) { > fork(); > } > > on a machine with no limits the load went to 290+ I tried fiddling with > limits and got it down to making the load 2-3 but the limits are ridiculous. > I didn't look in mail archives so sorry if this has been discussed before > > Luke > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message