From owner-freebsd-questions@FreeBSD.ORG Wed Mar 1 00:13:51 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 1622E16A420 for ; Wed, 1 Mar 2006 00:13:51 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id CADCA43D45 for ; Wed, 1 Mar 2006 00:13:50 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id AA8841A3C29; Tue, 28 Feb 2006 16:13:50 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E3CF651456; Tue, 28 Feb 2006 19:13:49 -0500 (EST) Date: Tue, 28 Feb 2006 19:13:49 -0500 From: Kris Kennaway To: Nikolas Britton Message-ID: <20060301001349.GA89407@xor.obsecurity.org> References: <058101c63ca5$585d0780$0300020a@mickey> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: Don O'Neil , 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:13:51 -0000 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 28, 2006 at 06:09:17PM -0600, Nikolas Britton wrote: > On 2/28/06, Don O'Neil wrote: > > What is the best way to 'burn in' or 'stress test' a new system w/ Free= BSD? > > I'd like to stress test the CPU, Memory, Disk, etc.. To make sure the > > hardware is 100% good before putting it in production. > > >=20 > 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. This is a bit hardcore, because as you note it sometimes finds kernel bugs so it's not going to be easy to identify the cause of problems. Kris --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEBOc9Wry0BWjoQKURAnz8AJ9oVoxhMrEjwc3IKf6x9CXuWSuQ2wCg9eCP COacheMRhMD0WsEHJaHZM4I= =qIv0 -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK--