ID: 11723
User Update by: [EMAIL PROTECTED]
Old-Status: Feedback
Status: Open
Bug Type: Scripting Engine problem
Operating system: linux 2.2.14 and 2.2.16
PHP Version: 4.0.6
Description: A few apache children remain in memory after apachectl stop

This is the line I used to configure the PHP:

./configure --enable-imap --enable-mysql --with-mysql --with-apache=../$APACHE 
--with-imap --without-xml --enable-track-vars --enable-memory-limit=yes 
--with-zlib=/usr --with-gd=/usr/local --with-jpeg-dir=/usr --with-png-dir=/usr 

The problem has presented only with PHP 4.0.5 (and 4.0.6) with apache 1.3.20. Before 
we had PHP 4.0.3pl1 with Apache 1.3.16 and we had no problems.

Soon as possible I'll try to give you a gdb track... this is difficult because often 
the machine is completely down and the only way to restart the apache is to reboot 
(power down) it...


Previous Comments:

[2001-06-27 11:56:50] [EMAIL PROTECTED]
what was the configure line used to configure PHP?


[2001-06-27 03:56:32] [EMAIL PROTECTED]
I have the same problem as Valerio (bug #11676), but in my case the apache children 
remain in memory and it is not possible to kill them (i've tried also kill -9 but 
nothing do to, sick!). The only way to solve the problem is to reboot the machine or, 
in the worst case, to power down hardly the system.
The kernels are 2.2.14 (RedHat 6.2) and 2.2.16 (RedHat 7.0)
, the apache is 1.3.20 and php 4.0.6 (but the problems were present also in php 4.0.5 
with apache 1.3.19).
I was not able to track down the bug, it seems to happen randomly.
The php is compiled with gd,mysql and imap (4.7c2).



Full Bug description available at:

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to