Red Hat Bugzilla – Bug 484058
Thread-safe php build
Last modified: 2014-09-15 07:41:08 EDT
The default PHP build is not thread-safe, and is hence unusable with the
"worker" MPM in httpd.
We could include an additional PHP build which is thread-safe, but has
fewer extensions enabled, and is incompatible with other packaged
extensions, but is suitable for simple sites.
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
I've made test packages available which should fix this issue. These
packages are unsupported, have not been through the standard Red Hat
QA process, and are not recommended for use on production systems.
Use of these packages may prevent you from (automatically) upgrading
to any asynchronous security errata which are issued before the
release of RHEL 5.5 due to version mismatches.
Please record any feedback on use of these test packages (positive or
negative!) on this bug report.
~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~
RHEL 5.5 Beta has been released! There should be a fix present in this
release that addresses your request. Please test and report back results
here, by March 3rd 2010 (2010-03-03) or sooner.
Upon successful verification of this request, post your results and update
the Verified field in Bugzilla with the appropriate value.
If you encounter any issues while testing, please describe them and set
this bug into NEED_INFO. If you encounter new defects or have additional
patch(es) to request for inclusion, please clone this bug per each request
and escalate through your support representative.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.