Date: Tue, 28 Feb 2006 19:13:49 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Nikolas Britton <nikolas.britton@gmail.com> Cc: Don O'Neil <don@lizardhill.com>, freebsd-questions@freebsd.org Subject: Re: System Burn In Message-ID: <20060301001349.GA89407@xor.obsecurity.org> In-Reply-To: <ef10de9a0602281609x9d3632fj6841d3869fd5a47d@mail.gmail.com> References: <058101c63ca5$585d0780$0300020a@mickey> <ef10de9a0602281609x9d3632fj6841d3869fd5a47d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <don@lizardhill.com> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060301001349.GA89407>