From owner-freebsd-bugs Sat Apr 28 19: 1:32 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from mail.viasoft.com.cn (unknown [61.153.1.177]) by hub.freebsd.org (Postfix) with ESMTP id 2CFDD37B423; Sat, 28 Apr 2001 19:01:28 -0700 (PDT) (envelope-from davidx@viasoft.com.cn) Received: from xyf ([192.168.1.204]) by mail.viasoft.com.cn (8.9.3/8.9.3) with SMTP id JAA14072; Sun, 29 Apr 2001 09:59:42 +0800 Message-ID: <00f901c0d050$96db7620$cc01a8c0@xyf> From: "David Xu" To: , References: <200104290125.f3T1PH393853@freefall.freebsd.org> Subject: Re: kern/26938: 4.3-stable is a broken kernel Date: Sun, 29 Apr 2001 10:03:30 +0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No, I don't think it's a reasonable answer, I think FreeBSD is goting fragility, before 4.3, I can never crash kernel in such way, I don't agree you to close this PR, the bug is caused by recent VM change, I want Matt or other kernel hackers to review this PR, Regards, David Xu ----- Original Message ----- From: To: ; ; Sent: Sunday, April 29, 2001 9:25 AM Subject: Re: kern/26938: 4.3-stable is a broken kernel > Synopsis: 4.3-stable is a broken kernel > > State-Changed-From-To: open->closed > State-Changed-By: greid > State-Changed-When: Sat Apr 28 18:19:40 PDT 2001 > State-Changed-Why: > You can also probably cause a FreeBSD machine to crash by striking > it repeatedly with a heavy object. > > I suggest you learn about limiting the resources allowed per-user; see > 'ulimit'. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=26938 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message