On Wed, 30 Aug 2000, Matt Sergeant wrote:
> On Wed, 30 Aug 2000, Stas Bekman wrote:
>
> > On Wed, 30 Aug 2000, Matt Sergeant wrote:
> >
> > > On Wed, 30 Aug 2000, Douglas Wilson wrote:
> > >
> > > > Forgive me if this is a stupid question, but I am rather
> > > > ignorant in regards to mod_per
On Wed, 30 Aug 2000, Stas Bekman wrote:
> On Wed, 30 Aug 2000, Matt Sergeant wrote:
>
> > On Wed, 30 Aug 2000, Douglas Wilson wrote:
> >
> > > Forgive me if this is a stupid question, but I am rather
> > > ignorant in regards to mod_perl, and I'm curious about
> > > something.
> > >
> > > If y
On Wed, 30 Aug 2000, Matt Sergeant wrote:
> On Wed, 30 Aug 2000, Douglas Wilson wrote:
>
> > Forgive me if this is a stupid question, but I am rather
> > ignorant in regards to mod_perl, and I'm curious about
> > something.
> >
> > If you reload modules, does that increase the size of the
> > f
On Wed, 30 Aug 2000, Douglas Wilson wrote:
> Forgive me if this is a stupid question, but I am rather
> ignorant in regards to mod_perl, and I'm curious about
> something.
>
> If you reload modules, does that increase the size of the
> forked children of the parent process? Or does just the
> pa
Forgive me if this is a stupid question, but I am rather
ignorant in regards to mod_perl, and I'm curious about
something.
If you reload modules, does that increase the size of the
forked children of the parent process? Or does just the
parent reload, with the children having to die and respawn?
This release adds the ability to specify modules to reload in the config
file as well as in the module itself. Docs below:
NAME
Apache::Reload - Reload changed modules
SYNOPSIS
In httpd.conf:
PerlInitHandler Apache::Reload
PerlSetVar ReloadAll Off
Then your module: