Bug#395929: libapache2-mod-suphp: Child processes eat 100% of the CPU instead of exiting

2006-11-07 Thread Emmanuel Lacour
On Tue, Nov 07, 2006 at 01:38:49AM +0100, Sebastian Marsching wrote: Stefan has written a patch that definitely addresses a problem in mod_suphp. However I have not yet had the time for testing the fixed version. Perhaps this patch solves the problem. However, maybe it only solves another

Bug#395929: libapache2-mod-suphp: Child processes eat 100% of the CPU instead of exiting

2006-11-06 Thread Sebastian Marsching
Stefan has written a patch that definitely addresses a problem in mod_suphp. However I have not yet had the time for testing the fixed version. Perhaps this patch solves the problem. However, maybe it only solves another problem I have not discovered yet. As the patch has been committed to

Bug#395929: libapache2-mod-suphp: Child processes eat 100% of the CPU instead of exiting

2006-11-06 Thread Stefan Siegel
The bug seems to be fixed in the current svn version available at https://ssl.marsching.biz/subversion/suphp/trunk/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#395929: libapache2-mod-suphp: Child processes eat 100% of the CPU instead of exiting

2006-11-05 Thread Stefan Siegel
For me this happens everytime a script exits whithout any output, e.g. a Perl CGI that does nothing or a PHP script that crashes before sending headers. The following PHP code kills itself and so triggers the bug: ?php posix_kill(posix_getpid(), 6); ? -- To UNSUBSCRIBE, email to [EMAIL

Bug#395929: libapache2-mod-suphp: Child processes eat 100% of the CPU instead of exiting

2006-10-28 Thread Sam Morris
Package: libapache2-mod-suphp Version: 0.6.1.20060928-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I backported 0.6.1.20060928-1 to sarge and found that after a few hours, load on the system would shoot up. Investigating, I saw dozens of apache2 processes owned by