From owner-freebsd-arch Mon Jul 10 1:44:24 2000 Delivered-To: freebsd-arch@freebsd.org Received: from snafu.adept.org (adsl-63-201-63-44.dsl.snfc21.pacbell.net [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id 97B2837C474; Mon, 10 Jul 2000 01:44:17 -0700 (PDT) (envelope-from mike@adept.org) Received: by snafu.adept.org (Postfix, from userid 1000) id 098CC9EE01; Mon, 10 Jul 2000 01:44:16 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id 025CA9B001; Mon, 10 Jul 2000 01:44:15 -0700 (PDT) Date: Mon, 10 Jul 2000 01:44:15 -0700 (PDT) From: BSD Biggot To: core-ix@hushmail.com Cc: freebsd-arch@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Some proposals to FreeBSD kernel In-Reply-To: <200007100823.BAA07998@mail3.hushmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 xxx -1 core-ix@hushmail.com wrote: > What he wrote was ' int main(void) {while(1) fork(); }' compiled it > and run it. Within a second /kernel said "proc: table is full" and > died. I tried this on some other BSD unixes and the result was > same. A fork() bomb... Resource exhaustion. Old news. > (BTW Minix 2.0 seem unaffected and probably other SVR4 > variants, because you can limit the number of system processes > and system still have resources to work fine(although slow)) I've done this on SunOS. As for limiting processes, I'd tweak the appropriate knobs in login.conf(5). If you're worried about root doing something similar without such restrictions... Well, you've got other things to worry about if someone already has root access to your machine. -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message