From owner-freebsd-questions@FreeBSD.ORG Wed Mar 1 00:09:19 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABE8216A420 for ; Wed, 1 Mar 2006 00:09:19 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19FFC43D48 for ; Wed, 1 Mar 2006 00:09:18 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by xproxy.gmail.com with SMTP id h29so3385wxd for ; Tue, 28 Feb 2006 16:09:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bHDooStcqHuZaAHhMEbUHwB43IjGhspWW0Vul8NZugdFoHsX1spNNPngEULMJWtOezqWlCfTXmYTQZYzmSP7Znb2iZ9dTcFPkSeJH117JLkiK+tYGt2tsmY366DB6Dh8Ehz5//S/ffgyzDpYFm3QRls3q6VssHkKN7pAU+i85bk= Received: by 10.70.54.13 with SMTP id c13mr1249355wxa; Tue, 28 Feb 2006 16:09:17 -0800 (PST) Received: by 10.70.65.9 with HTTP; Tue, 28 Feb 2006 16:09:17 -0800 (PST) Message-ID: Date: Tue, 28 Feb 2006 18:09:17 -0600 From: "Nikolas Britton" To: "Don O'Neil" In-Reply-To: <058101c63ca5$585d0780$0300020a@mickey> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <058101c63ca5$585d0780$0300020a@mickey> Cc: freebsd-questions@freebsd.org Subject: Re: System Burn In X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2006 00:09:19 -0000 On 2/28/06, Don O'Neil wrote: > What is the best way to 'burn in' or 'stress test' a new system w/ FreeBS= D? > I'd like to stress test the CPU, Memory, Disk, etc.. To make sure the > hardware is 100% good before putting it in production. > Maybe try http://www.holm.cc/stress/ but this would be like forkbombing. If the system locks it may be a kernel problem, not be a hardware problem. Check out UBCD, just type it into google. -- BSD Podcasts @ http://bsdtalk.blogspot.com/