> The question I had regards where to put the 'Apache::Reload' directive.
> The documentation suggests something like:
>
>
>
> PerlInitHandler Apache::Reload
> PerlSetVar ReloadAll Off
>
> PerlSetVar ReloadTouchFile /tmp/reload_modules
>
>
>
> The problem I see in a production mac
I've got a "reality check" question for
people to see that I'm not missing something obvious with our Apache::Reload
mod_perl setup.
We've recently install Apache::Reload at
our site in production and it's working great. In what is probably not the
best 'software engineering' style, we've
Can Apache::Reload be used to reload modules that are "use"-d by httpd PerlModule,
PerlRequire, or PerlHandler directives, or do they have to be explicitly "use"-d in
code that is inside a handler? I think the answer is "yes - these are no different
than anything else except that memory sharing
> However, now my logs are loaded with a ton of subroutine redefined
warnings
> (which is normal I suppose?). I can certainly live with this in a
> development environment, but thought I would check to see if it is
expected,
> and if it can be turned off while still enabling Reload.
Well, first
Of
Bryan Coon
Sent: Wednesday, August 01, 2001 9:36 AM
To: '[EMAIL PROTECTED]'
Subject: One more small Apache::Reload question
First, thanks to all the great suggestions, it looks like it works fine.
However, now my logs are loaded with a ton of subroutine redefined warnings
(which i
First, thanks to all the great suggestions, it looks like it works fine.
However, now my logs are loaded with a ton of subroutine redefined warnings
(which is normal I suppose?). I can certainly live with this in a
development environment, but thought I would check to see if it is expected,
and
