apache2-mpm-perchild breaks PHP4 installtion of libapache2-mod-php4

[Debian Bug Importer]

Automatically imported from Debian bug report #325553 http://bugs.debian.org/325553

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #325553 http://bugs.debian.org/325553

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Mon, 29 Aug 2005 14:08:20 +0200
From: =?iso-8859-1?q?J=FCrgen_Sauer?= <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: apache2-mpm-perchild breaks PHP4 installtion of libapache2-mod-php4

Package: apache2-mpm-perchild
Severity: critical
Justification: breaks unrelated software

It is impossible to install apache2-mpm-perchild and libapache2-mod-php4
together.

For Webhosting it is nessessary to us her to use AssignUserID which is a
apache2 option in apache2-mpm-perchild to upload things into the
customers own webspace and beeing able to divide users and their
webspaces.

apache2-mpm-perchild kicks out libapache2-mod-php4 during install!

greetings
J. Sauer

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.11.9-ax
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)

[Thom May (thombot)]

reassign 325553 libapache2-mod-php4
retitle 325553 PHP is not threadsafe.
kthxbye

Um.
PHP4 is, as the php group have said many times, is not known to be
threadsafe. Leaving aside how moronic this is, this means that a threaded
MPM like perchild cannot be safely used with the non threadsafe PHP4 module.
Your only reasonable solution is to use something like fastcgi or plain
suexec to run php4 scripts as cgis in the threaded MPM environment.
Also, severity inflation, which this is about as gratuitous a case as any
I've seen in a long time, does your cause no favours.
-Thom

[Steve Langasek (vorlon)]

# Automatically generated email from bts, devscripts version 2.9.4
severity 325553 wishlist

[Adam Conrad (adconrad)]

This is so obviously a non-bug (or a wishlist, which we already have filed).
perchild is a threaded webserver, php4 is non-threaded, they conflict on
purpose. Already closed with extreme prejudice in Debian. :)

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 30 Aug 2005 00:02:16 +0100
From: Thom May <email address hidden>
To: <email address hidden>
Subject: how about "no"?

reassign 325553 libapache2-mod-php4
retitle 325553 PHP is not threadsafe.
kthxbye

Um.
PHP4 is, as the php group have said many times, is not known to be
threadsafe. Leaving aside how moronic this is, this means that a threaded
MPM like perchild cannot be safely used with the non threadsafe PHP4 module.
Your only reasonable solution is to use something like fastcgi or plain
suexec to run php4 scripts as cgis in the threaded MPM environment.
Also, severity inflation, which this is about as gratuitous a case as any
I've seen in a long time, does your cause no favours.
-Thom

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Mon, 29 Aug 2005 16:36:32 -0700
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: severity of 325553 is wishlist

# Automatically generated email from bts, devscripts version 2.9.4
severity 325553 wishlist