From owner-freebsd-questions@FreeBSD.ORG Wed Jun 22 09:30:50 2005 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 E30BC16A41C for ; Wed, 22 Jun 2005 09:30:50 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8268143D1D for ; Wed, 22 Jun 2005 09:30:50 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.37.55] ([82.41.37.55]) by smtp-out2.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Wed, 22 Jun 2005 10:31:30 +0100 Message-ID: <42B92FC9.9030707@dial.pipex.com> Date: Wed, 22 Jun 2005 10:30:49 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.8) Gecko/20050530 X-Accept-Language: en, en-us, pl MIME-Version: 1.0 To: racerx@makeworld.com References: <20050621230339.B8497@neptune.atopia.net> <20050622075039.GH33633@osiris.chen.org.nz> <42B91F47.7020207@makeworld.com> In-Reply-To: <42B91F47.7020207@makeworld.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 22 Jun 2005 09:31:30.0899 (UTC) FILETIME=[2C277230:01C5770D] Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD dieing, now has died doing portsdb -uU 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, 22 Jun 2005 09:30:51 -0000 Chris wrote: >Jonathan Chen wrote: > > >>On Tue, Jun 21, 2005 at 11:04:44PM -0400, Matt Juszczak wrote: >> >> >> >>>Hi all, >>> >>>In relation to my previous post(s) (I no longer know the subject line), >>>my freebsd mail server died again, this time while I was doinga portsdb >>>-uU ... it got halfway through and crapped out. >>> >>> >>Check your hardware for overheating, power-supply problems and flakey >>memory chips. >> >> > >Agreed - we may indeed find out he's running an AMD. Can we say HOT?! > > > Have a look at http://www.silentpcreview.com/article169-page2.html (Heat and Power section). Kind of disagrees with you... --Alex