From owner-freebsd-arch Tue Nov 7 15:49:43 2000 Delivered-To: freebsd-arch@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 6D67D37B479; Tue, 7 Nov 2000 15:49:41 -0800 (PST) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 0EFBD1C83; Tue, 7 Nov 2000 18:49:41 -0500 (EST) Date: Tue, 7 Nov 2000 18:49:41 -0500 From: Bill Fumerola To: Andre Oppermann Cc: Paul Saab , Poul-Henning Kamp , arch@freebsd.org Subject: Re: Green/Yellow/Red state for the VM system. Message-ID: <20001107184940.X37870@jade.chc-chimes.com> References: <28041.973635706@critter> <3A088D1B.96157C0D@telehouse.ch> <20001107153343.A24788@elvis.mu.org> <3A0892BB.4F399708@telehouse.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A0892BB.4F399708@telehouse.ch>; from oppermann@telehouse.ch on Wed, Nov 08, 2000 at 12:39:39AM +0100 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 08, 2000 at 12:39:39AM +0100, Andre Oppermann wrote: > OK, but would the right solution be to simply make more memory > available? I doubt it. A bug is a bug and needs to be fixed not > to be masked. Eventually it would fail just in a different place. When you are being attacked / loosing resources to some big problem, any memory you make available is going to be eaten by the bug / attack. The trick is to change your behavior, not just use a bigger tool. -- Bill Fumerola - Lame Duck, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message