From owner-freebsd-questions@FreeBSD.ORG Wed Apr 26 14:16:07 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 2DD1916A407 for ; Wed, 26 Apr 2006 14:16:07 +0000 (UTC) (envelope-from hernan.silberman@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC20943D53 for ; Wed, 26 Apr 2006 14:16:02 +0000 (GMT) (envelope-from hernan.silberman@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so981956wxc for ; Wed, 26 Apr 2006 07:16:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=p3h6GjdFYjEAjCSh+fQZQqaSBYjwTzC0OMvRaUpShTFELoAiOe+YiEzwiJP8YK5ZpU2JyO29D9E5nbOfZ+FCMIbuNVwvdQnaeKjVFgyFBY58LHRP8xkn2UoEzJ+g15GlxuPcGiB2/qzqL4Sb9e560I2aKRHy9M/AOTnsLbsPDT8= Received: by 10.70.71.11 with SMTP id t11mr5413982wxa; Wed, 26 Apr 2006 07:16:01 -0700 (PDT) Received: by 10.70.53.2 with HTTP; Wed, 26 Apr 2006 07:16:01 -0700 (PDT) Message-ID: <9b9d376a0604260716p387c0612s71fe0b00a7f8a4c7@mail.gmail.com> Date: Wed, 26 Apr 2006 07:16:01 -0700 From: hernan To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: Horrible: Apache corrupting files? 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, 26 Apr 2006 14:16:07 -0000 >Please, check your RAM. I had similar problem with changing MD5 on PC with bad RAM. I had a similar problem that drove me crazy for a long while. It all made sense when I opened up the box and saw that the CPU fan was stopped. Luckily, there was no permanent damage to the CPU and replacing the fan make everything sane again. hernan