From owner-freebsd-hackers Fri May 14 7:57:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 9C35F150E5 for ; Fri, 14 May 1999 07:57:09 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id KAA23614; Fri, 14 May 1999 10:56:59 -0400 (EDT) Message-Id: <199905141456.KAA23614@cs.rpi.edu> To: Chuck Youse Cc: hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: 1GB, kvm issues. In-Reply-To: Message from Chuck Youse of "Fri, 14 May 1999 09:32:41 EDT." Date: Fri, 14 May 1999 10:56:59 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's been noted on several occasions that with large (> 256MB) of RAM, one > has to be "careful" with the configuration (NMBCLUSTERS, MAXUSERS) to > prevent the box from falling over every few days due to kvm problems. > > Can somebody be more specific? I'm just about to order a really, really > expensive machine and I want to be sure I can get it to work .. :) > > Chuck Youse This was fixed somewhere in the 3.1-STABLE branch, you will not need to worry about this at all with 3.2-BETA/3.2-RELEASE. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message