On Tue, 26 Oct 2004, Shane Caraveo wrote:
> Rasmus Lerdorf wrote:
> > On Tue, 26 Oct 2004, Wez Furlong wrote:
> >
> >>It should be safe to never ever dlclose() a module.
> >
> >
> > Do you mean never to dlclose() a module loaded via dl() at request time or
> > do you mean that in general it should
Rasmus Lerdorf wrote:
On Tue, 26 Oct 2004, Wez Furlong wrote:
It should be safe to never ever dlclose() a module.
Do you mean never to dlclose() a module loaded via dl() at request time or
do you mean that in general it should be safe to never dlclose() a module
even if it came in via an extension
Urgh.
On Tue, 26 Oct 2004 15:42:09 -0700 (PDT), Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> It's a bit tricky. When Apache starts up it does a double-pass of the
> conf files in order to do a syntax check. It needs to load all its
> modules in order to do this so our libphp4.so gets loaded which
On Tue, 26 Oct 2004, Wez Furlong wrote:
> On Tue, 26 Oct 2004 15:23:45 -0700 (PDT), Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> > On Tue, 26 Oct 2004, Wez Furlong wrote:
> > > It should be safe to never ever dlclose() a module.
> >
> > Do you mean never to dlclose() a module loaded via dl() at requ
On Tue, 26 Oct 2004 15:23:45 -0700 (PDT), Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> On Tue, 26 Oct 2004, Wez Furlong wrote:
> > It should be safe to never ever dlclose() a module.
>
> Do you mean never to dlclose() a module loaded via dl() at request time or
> do you mean that in general it shou
On Tue, 26 Oct 2004, Wez Furlong wrote:
> It should be safe to never ever dlclose() a module.
Do you mean never to dlclose() a module loaded via dl() at request time or
do you mean that in general it should be safe to never dlclose() a module
even if it came in via an extension line in the php.ini
