From owner-freebsd-questions@FreeBSD.ORG Wed Jun 15 18:50:10 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38DFB106567A for ; Wed, 15 Jun 2011 18:50:10 +0000 (UTC) (envelope-from feld@feld.me) Received: from mwi1.coffeenet.org (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id B10D18FC08 for ; Wed, 15 Jun 2011 18:50:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:To:Content-Type; bh=AwKhCA8EY5VPu4P3ns0BI1gbLVYTMFcdLY3VwtQvTAU=; b=r1viOlbvFikObYMMVjgWs+F2pjh6fjPaHYAoxU03a1WqeUBZ1p59Cx0/lAIHVfqia4Q5IHFiyYFn/Lny4nqgydL9NCtoCiOPKmuFyjG/IhXshMyDLbyqxKYfQQZQq0ND; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by mwi1.coffeenet.org with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QWvBk-000Kbv-CT for freebsd-questions@freebsd.org; Wed, 15 Jun 2011 13:51:40 -0500 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.3) with esmtpsa id 1308163894-46877-46875/6/4; Wed, 15 Jun 2011 18:51:34 +0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-questions@freebsd.org References: <3.0.1.32.20110615090401.0181fea8@sage-american.com> <3.0.1.32.20110615134015.01959568@sage-american.com> Date: Wed, 15 Jun 2011 13:50:01 -0500 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: <3.0.1.32.20110615134015.01959568@sage-american.com> User-Agent: Opera Mail/11.11 (FreeBSD) Subject: Re: Another PHP5 problem 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, 15 Jun 2011 18:50:10 -0000 On Wed, 15 Jun 2011 13:40:15 -0500, Jack L. Stone wrote: > I cannot do without ioncube as another post mentioned. I understand your need for ioncube, but replicate the problem to another non-production system and remove ioncube to see whether or not it is the cause. This is something we had to do and ultimately we told the only customer using ioncube they couldn't use it on our infrastructure anymore because it was a proprietary extension that causes issues. Again, before digging too deeply I strongly urge you repeat the test with ioncube extension disabled so you can rule that out immediately or else you'll be running around in circles for ages trying to figure out what the "cause" is. It's unfortunate that people think they need to obfuscate their code and use these silly workarounds. Regards, Mark