Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10946
Return-Path: <peter001@prolink.de>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 78627 invoked by uid 1010); 7 Jul 2004 12:46:13 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 78569 invoked from network); 7 Jul 2004 12:46:12 -0000
Received: from unknown (HELO Sol.prolink.de) (62.206.220.3)
  by pb1.pair.com with SMTP; 7 Jul 2004 12:46:12 -0000
Received: from [127.0.0.1] (mars [62.206.218.4])
	by Sol.prolink.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i67CjCMv017243
	for <internals@lists.php.net>; Wed, 7 Jul 2004 14:46:12 +0200
Message-ID: <40EBF03C.4050507@prolink.de>
Date: Wed, 07 Jul 2004 14:44:44 +0200
X-Accept-Language: de-de, en
MIME-Version: 1.0
To: internals@lists.php.net
References: <40EBCF77.7010007@prolink.de> <200407071345.10142.edink@emini.dk> <40EBEAC3.30809@prolink.de> <200407071426.59522.edink@emini.dk>
In-Reply-To: <200407071426.59522.edink@emini.dk>
X-Enigmail-Version: 0.84.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spamscreen: Protected by WatchGuard (WGTI) SpamScreen (TM)
	v7.2.B1501 Copyright (C) 1996-2004 WGTI
X-Virus-Scanned: clamd / ClamAV version 0.73, clamav-milter version 0.73a
	on Sol.prolink.de
X-Virus-Status: Clean
Subject: Re: [PHP-DEV] Setting memory_limit fails
From: peter001@prolink.de (Peter Rendl)

Edin Kadribasic wrote:

> You have uncovered an error in win32 configure script which is fixed now. The 
> next snap should again have memory limit disabled.

This is good, thank you.

One more question for my understanding:
Checking the memory limit and setting it, are 2 different things to me. 
Why did "php -n -d memory_limit=32M" not set the limit to 32MB?

-Peter