From owner-freebsd-questions@FreeBSD.ORG  Wed Jan  8 13:38:45 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 445DFFA8
 for <freebsd-questions@freebsd.org>; Wed,  8 Jan 2014 13:38:45 +0000 (UTC)
Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 01CB1199D
 for <freebsd-questions@freebsd.org>; Wed,  8 Jan 2014 13:38:44 +0000 (UTC)
Received: from r56.edvax.de (port-92-195-149-155.dynamic.qsc.de
 [92.195.149.155])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx01.qsc.de (Postfix) with ESMTPS id 1E7CB3D98D;
 Wed,  8 Jan 2014 14:38:37 +0100 (CET)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id s08DcCON002086;
 Wed, 8 Jan 2014 14:38:12 +0100 (CET) (envelope-from freebsd@edvax.de)
Date: Wed, 8 Jan 2014 14:38:12 +0100
From: Polytropon <freebsd@edvax.de>
To: kpneal@pobox.com
Subject: Re: Server hang
Message-Id: <20140108143812.bcfc9a75.freebsd@edvax.de>
In-Reply-To: <20140107211012.GA47988@neutralgood.org>
References: <CALeO_hORJin5OOkA45fG+HFrai6XhPpOob4u-NhnJkLGyorvhA@mail.gmail.com>
 <20140106182826.28018a2f@X220.alogt.com>
 <CALeO_hMOhe_Cf0NQa6p0wrHC7LdA7r6SwkZCOUrqjYUO=sPUYA@mail.gmail.com>
 <alpine.BSF.2.00.1401061303340.24851@mail.fig.ol.no>
 <CALeO_hO=NaErzsY3N0KuDmzE_WkMwms9pp-L14h=Hb0eheCKtQ@mail.gmail.com>
 <20140107085545.06310df9.freebsd@edvax.de>
 <CALeO_hN81jxUvf_Q4kLHL0+wWxn-7V42=CeFsxod6fawbFB2PA@mail.gmail.com>
 <20140107115216.1f06587d.freebsd@edvax.de>
 <20140107211012.GA47988@neutralgood.org>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Polytropon <freebsd@edvax.de>
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 13:38:45 -0000

On Tue, 7 Jan 2014 16:10:12 -0500, kpneal@pobox.com wrote:
> So a memory tester
> cannot tell if a stick of memory is _good_; it can only tell that it is
> _bad_.

That is a very good summary.

To add some science-y statement: It will tell you that memory
is bad in _finite_ time, but requires infinite time to make
sure it's actually good by running (without end). :-)



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...