From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 17:02:37 2005 Return-Path: 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 BBBA116A4CE for ; Tue, 22 Mar 2005 17:02:37 +0000 (GMT) Received: from fusion.vilot.net (vilot.com [64.246.32.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62DDF43D46 for ; Tue, 22 Mar 2005 17:02:37 +0000 (GMT) (envelope-from tom@vilot.com) Received: from vilot.com (c-24-8-184-241.client.comcast.net [24.8.184.241]) (authenticated bits=0) by fusion.vilot.net (8.13.1/8.12.9) with ESMTP id j2MH2ZnZ075023; Tue, 22 Mar 2005 11:02:35 -0600 (CST) (envelope-from tom@vilot.com) Received: by vilot.com (sSMTP sendmail emulation); Tue, 22 Mar 2005 10:02:34 -0700 From: "Tom Vilot" Date: Tue, 22 Mar 2005 10:02:34 -0700 To: Peter Risdon Message-ID: <20050322170234.GA1576@vilot.com> References: <20050322162216.GA1354@vilot.com> <1111509994.751.306.camel@lorna.circlesquared.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1111509994.751.306.camel@lorna.circlesquared.com> User-Agent: Mutt/1.4.2.1i Organization: 3Dimentia, Inc. Mailer: mutt for FreeBSD cc: "freebsd-questions@freebsd.org" Subject: Re: PHP / Apache bus error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 17:02:37 -0000 > But then, I've found most apache/php errors actually derive from some > php extension and this can be traced by a process of elimination. It's > often then a dependency of the extension that has been updated, or > something. I'm starting to think there's something funky about PHP and MySQL. > > Is this something that will clear up if I move to FreeBSD 5.3? Or is > > there some other known work-around? I ask because I have a 5.3 box here > > at home that does not seem to be exhibiting this behavior. > Yes, but going to 4.11 should fix it as well. Can you explain why? What is it about 4.11 vs 4.9 with regard to this issue?