From owner-freebsd-stable@FreeBSD.ORG Sat Dec 23 00:21:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B08C416A407 for ; Sat, 23 Dec 2006 00:21:43 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 37DA213C41A for ; Sat, 23 Dec 2006 00:21:42 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id kBN0LfFj076046; Fri, 22 Dec 2006 21:21:41 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-stable@freebsd.org Date: Fri, 22 Dec 2006 21:22:49 -0300 User-Agent: KMail/1.9.4 References: <000801c723bb$efc2b540$260ba8c0@wii.wintecind.com> <200612220259.kBM2xYxc019408@khavrinen.csail.mit.edu> <20061222051513.GK63341@manor.msen.com> In-Reply-To: <20061222051513.GK63341@manor.msen.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200612222122.50217.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Cc: "Michael R. Wayne" Subject: Re: Possibility for FreeBSD 4.11 Extended Support X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Dec 2006 00:21:43 -0000 On Friday 22 December 2006 02:15, Michael R. Wayne wrote: > FreeBSD 4.11 can survive a simple burn-in test. =A0FreeBSD 5.X and > 6.1 can not. =A0Here's what I wrote earlier. > burn-in usually is a hardware test and not a software test > =A0 =A0Take a server. =A0Configure for SMP, add quotas within jails and > =A0 =A0basic IPFW protection with a few hundred dummynet pipes for b/w > =A0 =A0throttling (less than 10,000 total IPFW lines). =A0Load the machine > =A0 =A0a bit so that it constantly maintains a 3 digit load and run > =A0 =A0sufficient active processes to keep it in moderate swap state. let's then qualify cars by how much miles they stand with a flat tire ... a= ny=20 practical value here? So anybody tries to get a server away from swap and y= ou=20 keep it in swap state ... funny theories you have >=A0 =A0The result of that minimal-effort test yields machines which can >=A0 =A0not maintain 30 days of uptime (most fail in under a week). ahem ... faulty memory or what? http://suporte.matik.com.br/swap-3-year.png =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br