Your message dated Mon, 10 Mar 2014 11:51:33 +0100
with message-id 
<[email protected]>
and subject line Re: [php-maint] Bug#539058: php5: memory_limit = 128M, 
MaxClients = 150
has caused the Debian Bug report #539058,
regarding php5: memory_limit = 128M, MaxClients = 150
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
539058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539058
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: php5
Version: 5.3.0-2
Severity: normal

Hi,

/etc/php5/apache2/php.ini:
memory_limit = 128M

/etc/apache2/apache2.conf:
MaxClients = 150

128 m * 150 = 19 g

That's gonna be fun! ;)

Greetings,

Olaf

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages php5 depends on:
ii  libapache2-mod-php5           5.3.0-2    server-side, HTML-embedded scripti
ii  php5-cgi                      5.3.0-2    server-side, HTML-embedded scripti
ii  php5-common                   5.3.0-2    Common files for packages built fr

php5 recommends no packages.

php5 suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
On Tue, July 28, 2009 20:25, Olaf van der Spek wrote:
> Package: php5
> Version: 5.3.0-2
> Severity: normal
>
> Hi,
>
> /etc/php5/apache2/php.ini:
> memory_limit = 128M
>
> /etc/apache2/apache2.conf:
> MaxClients = 150
>
> 128 m * 150 = 19 g
>
> That's gonna be fun! ;)

As indicated in the bug log, the 128m is only an upper limit; and it's a
default configurtion, that has hardly let to any concrete problems in the
past 5 years since this bug was filed. It's the administrator's
responsibility to configure the limits that fit their specific available
resources.

Oh, and even then, 19G is of course for current machines not that much
anymore anyway.


Cheers,
Thijs

--- End Message ---

Reply via email to