From owner-freebsd-bugs Wed Feb 16 0:39:40 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by builder.freebsd.org (Postfix) with ESMTP id 9654843E7 for ; Wed, 16 Feb 2000 00:39:38 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id AAA58292; Wed, 16 Feb 2000 00:40:10 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Wed, 16 Feb 2000 00:40:10 -0800 (PST) Message-Id: <200002160840.AAA58292@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/16568: How to crash FreeBSD 4.4 Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/16568; it has been noted by GNATS. From: Sheldon Hearn To: bg@bg.sics.se Cc: FreeBSD-gnats-submit@FreeBSD.ORG, bg@sics.se Subject: Re: kern/16568: How to crash FreeBSD 4.4 Date: Wed, 16 Feb 2000 10:39:31 +0200 On Mon, 07 Feb 2000 20:07:43 +0100, Bjoern Groenvall wrote: > Compile and run the following program. If you don't get a panic on the > first try, Ctrl-C and rerun. It looks like an obfuscated fork-bomb, which is nothing new and can be controlled with the maxproc capability in login.conf(5). Could you please try this in a session for which "max user processes" (as reported by ulimit -a) is limited to some sane number and provide feedback? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message