Re: Unexpected Extension Deinitializing on Startup
| From: | Rasmus Lerdorf | Date: | Fri, 20 Apr 2007 08:57:45 +0000 |
| Subject: | Re: Unexpected Extension Deinitializing on Startup | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-28932@lists.php.net to get a copy of this message | ||
Michael B Allen wrote:
> On Fri, 20 Apr 2007 09:20:26 +0200 (CEST)
> Derick Rethans <derick@php.net> wrote:
>
>> On Thu, 19 Apr 2007, Michael B Allen wrote:
>>
>>> Is there an Apache or PHP setting that would cause an extension to be
>>> deinitilized in the initial root process on startup?
>> It's an Apache thing. First it brings up all modules (like mod_php) to
>> figure out which settings it supports. Then it shuts down everything.
>> Then it starts the real start up process and initializes all modules
>> again.
>
> Hi Derick,
>
> Is this behavior documented anywhere? I suppose I should just get on
> the Apache list and ask there ...
This question has probably been asked a hundred times on the Apache
lists. There really isn't much decent documentation out there on how to
write Apache modules. The Apache1 code is rather simple, so most people
just read the server code to figure it out. The closest thing to real
documentation is an old book called "Writing Apache Modules with Perl
and C" by Lincoln Stein and Doug MacEachern. You'll want to read
chapter 3 - "The Apache Module Architecture and API" where this
particular topic is covered.
-Rasmus