From owner-freebsd-questions Tue Mar 11 00:39:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA06585 for questions-outgoing; Tue, 11 Mar 1997 00:39:49 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA06580 for ; Tue, 11 Mar 1997 00:39:46 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id AAA08156; Tue, 11 Mar 1997 00:39:57 -0800 (PST) To: Samara McCord cc: freebsd-questions@freebsd.org Subject: Re: make world exposes memory errors!? In-reply-to: Your message of "Mon, 10 Mar 1997 23:20:40 PST." <199703110720.XAA13364@syzygy.zytek.com> Date: Tue, 11 Mar 1997 00:39:56 -0800 Message-ID: <8152.858069596@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Assuming this is a memory problem, my question is: how is it that this machin e, > which has been running continuously for six months as a server, several domai ns > and websites and some heavy computational processing could avoid finding this > problem while "make world" would expose it? Is there something peculiar > going on here that would stress the system differently than normal usage? Not peculiar, but certainly more stress over a shorter period than most machines seem to experience any other way. The `make world' is a well accepted quality-assurance test for most FreeBSD hardware vendors now, and I know that I certainly won't check off a box as "seaworthy" until it's passed two consecutive make worlds. Nowadays, with machines as fast as they are, I might even consider running 4 or 5 of them over a 24 hour period and test the thermal sensitivity of the system at the same time. Jordan