Re: Unexpected Extension Deinitializing on Startup

On Fri, 20 Apr 2007 01:57:45 -0700 Rasmus Lerdorf <rasmus@lerdorf.com> wrote: > 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. Well it doesn't sound like this is something they just started doing. My PHP extension has been tested on numerous platforms and I have only ever seen the PHP module initialization / deinitialization routines called once on startup / shutdown. Even if the actual PHP module is loaded and unloaded, do you call the (de)initialization routines for each (unl)load? I'm not sure this issue is the issue I'm seeing. Mike -- Michael B Allen PHP Active Directory Kerberos SSO http://www.ioplex.com/