Re: pkg/32007: FreeBSD and PHP problem with --enable-memory-limit

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

The following reply was made to PR pkg/32007; it has been noted by GNATS.

From: Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: pkg/32007: FreeBSD and PHP problem with --enable-memory-limit
Date: Sun, 6 Nov 2005 16:06:17 +0100

 On Sat, Nov 05, 2005 at 11:51:02PM +0000, Lubomir Sedlacik wrote:
 >  
 >  On Sat, Nov 05, 2005 at 11:33:00PM +0000, pancake%phreaker.net@localhost 
 > wrote:
 >  > The fix contains just a bigger limit for PHP, something like 64M is so
 >  > logic, but disable --disable-memory-limit would make the same effect
 >  > on ther target system. But obviously making the system 'vulnerable' to
 >  > a DoS. (sysctl fixable).
 >  >=20
 >  > =09
 >  > --- Makefile.php        1 Nov 2005 23:12:15 -0000       1.30
 >  > +++ Makefile.php        5 Nov 2005 23:24:03 -0000
 >  > @@ -22,7 +22,7 @@
 >  > =20
 >  > -CONFIGURE_ARGS+=3D       --enable-memory-limit
 >  > +CONFIGURE_ARGS+=3D       --enable-memory-limit=3D64M
 >  
 >  i don't think we should be patching it here.  it is very site specific.
 >  feel free to adjust the "memory_limit" setting in your php.ini.
 
 While I agree that changing the default memory limit is site-specific, I
 think the failure is hard enough to correctly detect. What do you think
 about adding a (OS specific) warning to MESSAGES?
 
 Joerg