Re: Considering segfaults: how to protect other requests?
| From: | Kārlis Repsons | Date: | Sat, 21 Jan 2012 20:27:20 +0000 |
| Subject: | Re: Considering segfaults: how to protect other requests? | ||
| References: | 1 2 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-9056@lists.php.net to get a copy of this message | ||
On 01/21/2012 08:27 PM, Rasmus Lerdorf wrote:
> One of the big benefits of not relying on a multi-threaded architecture
> is that each preforked httpd (or php-fpm) process has its own separate
> memory space managed by the kernel. In an MT architecture you have to do
> your own memory management. I much prefer letting the kernel keep me
> safe. So yes, if something corrupts memory and an httpd process
> segfaults, there is no bleed-over into other httpd processes. This is an
> architectural feature, not a fluke.
Does just running Apache with prefork MPM warrants that each request for
a functionality of the same PHP extension will be isolated from all
other requests?
What should I read about Apache and PHP first to do extension
development? Currently I'm just having some C/C++ examples and Apache is
a black box to me...