On Fri, 20 Apr 2007 01:57:45 -0700
Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> Michael B Allen wrote:
> > On Fri, 20 Apr 2007 09:20:26 +0200 (CEST)
> > Derick Rethans <[EMAIL PROTECTED]> wrote:
> >
> >> On Thu, 19 Apr 2007, Michael B Allen wrote:
> >>
> >>> Is there an Apache or PHP setting that
Michael B Allen wrote:
> On Fri, 20 Apr 2007 09:20:26 +0200 (CEST)
> Derick Rethans <[EMAIL PROTECTED]> 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?
>> I
On Fri, 20 Apr 2007, Michael B Allen wrote:
> On Fri, 20 Apr 2007 09:20:26 +0200 (CEST)
> Derick Rethans <[EMAIL PROTECTED]> 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
On Fri, 20 Apr 2007 09:20:26 +0200 (CEST)
Derick Rethans <[EMAIL PROTECTED]> 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 i
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 d
Is there an Apache or PHP setting that would cause an extension to be
deinitilized in the initial root process on startup?
We have an extension that forks a process from the initial Apache root
process and does privileged work. The regular Apache workers running as
'apache' communicate with this r
