From owner-freebsd-ports@FreeBSD.ORG  Thu Mar  3 08:08:19 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9CF7316A4CE; Thu,  3 Mar 2005 08:08:19 +0000 (GMT)
Received: from netgecko.info (p15089742.pureserver.de [217.160.92.122])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id BFB2A43D5D; Thu,  3 Mar 2005 08:08:18 +0000 (GMT)
	(envelope-from alex@kiesel.name)
Received: from boost.home.ahk (p3E991AFC.dip0.t-ipconnect.de [62.153.26.252])
	by netgecko.info (Postfix) with ESMTP id 0CEAE892D8;
	Thu,  3 Mar 2005 09:14:53 +0100 (CET)
From: Alex Kiesel <alex@kiesel.name>
To: Roman Neuhauser <neuhauser@chello.cz>
In-Reply-To: <20050303074015.GA704@isis.wad.cz>
References: <20050303074015.GA704@isis.wad.cz>
Content-Type: text/plain
Date: Thu, 03 Mar 2005 09:09:03 +0100
Message-Id: <1109837343.586.3.camel@boost.home.ahk>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
cc: ports@freebsd.org
cc: ale@freebsd.org
Subject: Re: lang/php4-cli: --enable-memory-limit in CONFIGURE_ARGS?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2005 08:08:19 -0000

On Thu, 2005-03-03 at 08:40 +0100, Roman Neuhauser wrote:
> Hello,
> 
> can the lang/php4 port be modified so that the cli version of php is
> configured without --enable-memory-limit in CONFIGURE_ARGS? It only
> makes sense in the apache/cgi SAPIs, and is quite strange in a command
> line tool (twice so with the default limit of 8MB).
> 
> A workaround is to set the limit in php-cli.ini to a very high number,
> but there's still a (small) performance impact.

You can set it to 0 to have no restriction at all (except real memory).
Performance impact, of course, remains.

-Alex