From owner-freebsd-bugs Wed Feb 16 5:29:33 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 DA3E93D39 for ; Wed, 16 Feb 2000 05:29:28 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id FAA79653; Wed, 16 Feb 2000 05:30:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Wed, 16 Feb 2000 05:30:02 -0800 (PST) Message-Id: <200002161330.FAA79653@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Thomas David Rivers Subject: Re: kern/16568: How to crash FreeBSD 4.4 Reply-To: Thomas David Rivers 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: Thomas David Rivers To: rivers@dignus.com, sheldonh@uunet.co.za Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/16568: How to crash FreeBSD 4.4 Date: Wed, 16 Feb 2000 08:25:57 -0500 (EST) > > > On Wed, 16 Feb 2000 07:12:17 EST, Thomas David Rivers wrote: > > > Even if it is a modified fork-bomb - should FreeBSD panic? I wouldn't > > think so... > > Panic? I don't see any panic described in the PR. Oh, _there_... he > mentions a panic under How-To-Repeat. > > Well, it'd be swell if he'd show us the panic. I suppose so, although the how-to-repeat is there. Perhaps there's an expectation that someone will repeat the problem. But, I agree - more information is very rarely the wrong thing to do. > Meantime, I'll try to > read slower. :-) Yeah, I know exactly what you mean :-) - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message