From owner-freebsd-hackers Fri May 14 8:34:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 3713B14D10 for ; Fri, 14 May 1999 08:34:12 -0700 (PDT) (envelope-from eagle@phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with ESMTP id KAA31582; Fri, 14 May 1999 10:32:23 -0400 (EDT) (envelope-from eagle@phc.igs.net) X-Authentication-Warning: eagle.phc.igs.net: eagle owned process doing -bs Date: Fri, 14 May 1999 10:32:23 -0400 (EDT) From: Rob Garrett To: "David E. Cross" Cc: Chuck Youse , hackers@FreeBSD.ORG Subject: Re: 1GB, kvm issues. In-Reply-To: <199905141456.KAA23614@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 May 1999, David E. Cross wrote: > > 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. > I thought so as well, however I added a 64 meg dimm and ran into the same problems he is describing. After I remembered the problem. I lowered the value of maxusers and everything is back to normal. This is on 4.0 - Current. btw.. 1 - 128 meg dimm 1 - 64 meg dimm and for the record 750 meg of swap space rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message