Date: Tue, 8 May 2001 10:40:43 +0800 From: David Xu <davidx@viasoft.com.cn> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: greid@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re[2]: kern/26938: 4.3-stable is a broken kernel Message-ID: <736972826.20010508104043@viasoft.com.cn> In-Reply-To: <200105021548.LAA93708@khavrinen.lcs.mit.edu> References: <200104290125.f3T1PH393853@freefall.freebsd.org> <200105021548.LAA93708@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Garrett, Wednesday, May 02, 2001, 11:48:53 PM, you wrote: GW> <<On Sat, 28 Apr 2001 18:25:17 -0700 (PDT), <greid@FreeBSD.ORG> said: >> State-Changed-From-To: open->closed >> 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'. GW> This is an inappropriate response. Any kernel panic indicates a bug GW> (although perhaps not one that is easily fixed). GW> -GAWollman Hi, I have 64M RAM, I found if I use GENERIC config(maxusers is 32), thing's fine. but if I change maxusers to 128, the bug can be trigged by a fork bomb reported in PR. the the problem is related to RAM size and maxuser parameters. -- Best regards, David mailto:davidx@viasoft.com.cn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?736972826.20010508104043>