Ugh! Not use to lists that reply to author.
Okay to resay what I sent to Geoffrey.
using the -I switch in the config file works, unlike the PerlSetEnv PERL5LIBGeoffrey Young [EMAIL PROTECTED] wrote:
Here's my perl.conf (sourced by httpd.conf) start LoadModule perl_module
I'm trying to do some development work with mod_perl and find restarting the server a pain. So I setup Apache::Reload, but it doesn't seem to want to see my local devel directory all the time.Here's my settingsApache/2.0.40mod_perl-1.99_7Linux 2.4.20-8 (RedHat9 I think)Here's my perl.conf
Bruce Tennant wrote:
I'm trying to do some development work with mod_perl and find
restarting the server a pain. So I setup Apache::Reload, but it
doesn't seem to want to see my local devel directory all the time.
Here's my settings
Apache/2.0.40
mod_perl-1.99_7
please upgrade to the latest CVS
Here's my perl.conf (sourced by httpd.conf)
start
LoadModule perl_module modules/mod_perl.so
PerlSetEnv PERL5LIB /home/bruce/public_html/ffball/myff
on second thought, try
PerlSwitches -I/home/bruce/public_html/ffball/myff
or
PerlSwitches
Forwarding message as I didn't realize I was missing the list.
Geoffrey Young [EMAIL PROTECTED] wrote:
Date: Tue, 12 Aug 2003 14:18:37 -0400From: Geoffrey Young <[EMAIL PROTECTED]>To: Bruce Tennant <[EMAIL PROTECTED]>Subject: Re: Apache::Reload and INC path partialy workingok, I'll
Hi Folks
Fascinating to see this on a non-Windows box.
Reloading modules after they have been editied, eg httpd like so:
PerlModule Apache::Reload
PerlInitHandler Apache::Reload
PerlSetVar ReloadAll Off
PerlSetVar ReloadModules CGI CGI::Application ... Sweep::*
works about 99% of the time
I've been working
with Apache::Reload and Registry and have been unable to get any cache flushing
to work. (I've added debug messages in Registry to show cache use or
reloading).
I've tried this
combination: (httpd.conf)
PerlModule
Apache::RegistryPerlModule
Apache::StatusPerlInitHandler
On Fri, 2003-08-01 at 11:10, Roger Davenport wrote:
I've been working with Apache::Reload and Registry and have been
unable to get any cache flushing to work. (I've added debug messages
in Registry to show cache use or reloading).
Can you tell us what you are trying to reload and how you know
--- Original Message ---
From: Stas Bekman [EMAIL PROTECTED]
To: Ron Savage [EMAIL PROTECTED]
Cc:
Sent: Sat, 01 Mar 2003 12:47:39 +1100
Subject: Re: [MP2] Apache::Reload date bug
Ron Savage wrote:
On Tue, 25 Feb 2003 09:40:05 +1100, Stas Bekman wrote:
Hi Stas
Output when run as /perl/main.cgi
On Wed, 26 Feb 2003 22:30:51 -0600 (CST), Randy Kobes wrote:
On Thu, 27 Feb 2003, Ron Savage wrote:
On Wed, 26 Feb 2003 09:23:39 +1100, Stas Bekman wrote:
HI Randy
The mod_perl 2 ppm package (for ActivePerl 8xx) at
http://theoryx5.uwinnipeg.ca/ppms/ is updated
periodically with a cvs build - as
On Wed, 26 Feb 2003 09:23:39 +1100, Stas Bekman wrote:
Hi Stas
Have you tried the current mod_perl cvs?
No. Being usually a Windows (shudder) user, I wait for Randy to issue
a build.
Today I spent 4 hours failing to install Red Hat 6, Red Hat 8 and
Mandrake 9 on a brand new Dell with a
On Thu, 27 Feb 2003, Ron Savage wrote:
On Wed, 26 Feb 2003 09:23:39 +1100, Stas Bekman wrote:
Hi Stas
Have you tried the current mod_perl cvs?
No. Being usually a Windows (shudder) user, I wait for Randy to issue
a build.
The mod_perl 2 ppm package (for ActivePerl 8xx) at
Ron Savage wrote:
On Tue, 25 Feb 2003 09:40:05 +1100, Stas Bekman wrote:
And what your error_log says?
Nothing is output to the error_log.
Have you tried the current mod_perl cvs?
__
Stas BekmanJAm_pH -- Just
IfModule mod_perl.c
PerlModule Apache::Reload
PerlInitHandler Apache::Reload
PerlSetVar ReloadAll Off
PerlSetVar ReloadModules CGI::Explorer DBIx::AdminEngine Monash::*
Sweep::*
#PerlSwitches -Mblib=C:\Apache2
PerlRequire C:/Apache2/conf/startup.pl
Alias /perl/ C:/Apache2/perl/
Location /perl
Ron Savage wrote:
On Wed, 19 Feb 2003 10:04:02 +1100, Stas Bekman wrote:
Ron Savage wrote:
On Tue, 18 Feb 2003 12:56:38 +1100, Stas Bekman wrote:
Hi Folks
In endeavouring to reproduce this problem, I've encountered another:
main.cgi:
-8-
#!/usr/bin/perl
use strict;
use warnings;
use
On Tue, 25 Feb 2003 09:40:05 +1100, Stas Bekman wrote:
And what your error_log says?
Nothing is output to the error_log.
--
Cheers
Ron Savage, [EMAIL PROTECTED] on 25/02/2003
http://savage.net.au/index.html
Ron Savage wrote:
On Tue, 18 Feb 2003 12:56:38 +1100, Stas Bekman wrote:
perl -le 'warn(foo\n)'
You got the quotes wrong for MS Windows, so I ran it twice:
C:\Backupperl -le warn(qq|foo\n|)
foo
C:\Backupperl -le 'warn(foo\n)'
well, you've got the idea, right.
Perhaps someone on win32
, you've got the idea, right.
Perhaps someone on win32 can try to debug the behavior that you
saw. I can't reproduce it on my linux box.
With my ActivePerl 8xx compatible perl-5.8, sticking in a
warn(foo\n);
inside a simple handler that uses Apache::Reload
just output foo in the error log
)'
well, you've got the idea, right.
Perhaps someone on win32 can try to debug the behavior that you
saw. I can't reproduce it on my linux box.
With my ActivePerl 8xx compatible perl-5.8, sticking in a
warn(foo\n);
inside a simple handler that uses Apache::Reload
just output foo in the error
For those who started working with mp2 and found themselves unable to use
Apache::Reload for connection filters and protocol handlers, I'm happy to tell
you that the cvs version now supports Apache::Reload in the
PerlPreConnectionHandler phase, which happens as early as possible. The
updated
Folks
I don't know if this an Apache problem, or a mod_perl problem.
Apache::Reload outputs a UTC date rather than a local date, when it
encounters an error. Here's an excerpt from my log.
Notice how the dates go Sun, Mon, ..., Sun.
[Sun Feb 16 18:31:25 2003] [error] [client 127.0.0.1
Igor Vylusko wrote:
in doc
http://perl.apache.org/docs/2.0/api/mod_perl-2.0/Apache/Reload.html
declared that when using Apache::Reload I may define additional lib
in httpd.conf: PerlSetEnv PERL5LIB /home/httpd/perl/extra
But when I enable PerlInitHandler Apache::Reload in config all libs defined
be useful in both mod_perl
1.* and 2.0,
can it be applied to both distributions? I don't quite understand why
installing
Apache::Reload from CPAN will cause mod_perl2.0 to be installed, but I'll
try to think some more about it.
Because Apache::Reload is distributed on CPAN and is not a part
Hi All,
in doc
http://perl.apache.org/docs/2.0/api/mod_perl-2.0/Apache/Reload.html
declared that when using Apache::Reload I may define additional lib
in httpd.conf: PerlSetEnv PERL5LIB /home/httpd/perl/extra
But when I enable PerlInitHandler Apache::Reload in config all libs defined in
PERL5LIB
Igor Vylusko wrote:
Hi All,
in doc
http://perl.apache.org/docs/2.0/api/mod_perl-2.0/Apache/Reload.html
declared that when using Apache::Reload I may define additional lib
in httpd.conf: PerlSetEnv PERL5LIB /home/httpd/perl/extra
But when I enable PerlInitHandler Apache::Reload in config all libs
in doc
http://perl.apache.org/docs/2.0/api/mod_perl-2.0/Apache/Reload.html
declared that when using Apache::Reload I may define additional lib
in httpd.conf: PerlSetEnv PERL5LIB /home/httpd/perl/extra
But when I enable PerlInitHandler Apache::Reload in config all libs defined in
PERL5LIB
I started using a dynamic INC (set up in a TransHandler), and discovered
that Apache::Reload (v0.07) was not doing its job correctly in that case.
Note, changing INC in a transhandler won't have the desired Apache::Reload
effects unless the PerlInitHandler for Apache::Reload is placed
I've been successfully using Apache::Reload for a few weeks now. However, I
installed it on my home development system, and I'm getting this error when
accessing a module that contains 'use Apache::Reload':
[Mon Aug 26 09:59:12 2002] [error] Can't locate main.pm in INC (INC
contains
* Ken Miller [EMAIL PROTECTED] [2002-08-26 12:03]:
What's main.pm, and why can't Apache::Reload find it? I've searched
the archives, but have had little success in finding anything
interesting.
Run
find $dir -name 'main.pm' -print
For each dir in @INC, and see what comes up.
(darren
Ken Miller wrote:
I've been successfully using Apache::Reload for a few weeks now. However, I
installed it on my home development system, and I'm getting this error when
accessing a module that contains 'use Apache::Reload':
[Mon Aug 26 09:59:12 2002] [error] Can't locate main.pm in @INC
[...]
Anyway, I decided to add another directive to Apache::Reload
PerlSetVar ReloadDirectories /site/lib /usr/local/apache/conf
Apache::Reload allows you to define which modules to reload using the
patterns like so:
PerlSetVar ReloadAll Off
PerlSetVar ReloadModules Apache::* My
ReloadDebug's output that those cached files are being checked by
Apache::Reload,
and if they have been modified - they'll be reloaded. The problem is, if the code has
a syntax
error, that error will occur when Apache::Reload re-require()s that file, and the
error message
will be printed to a log
Reports to ReloadModules, and
restart the server.
That's the thing. It's a good idea to alway use some prefix package name
in all your modules, to avoid future clashes with other modules. And it
automatically solves your problem with Apache::Reload.
2. Much more obscure, related to HTML
a good idea to alway use some prefix package
name in all your modules, to avoid future clashes with other modules.
And it automatically solves your problem with Apache::Reload.
2. Much more obscure, related to HTML::Mason. As I mentioned in my
post:
In Mason components are precompiled
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 isprobably not the
best 'software engineering' st
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 machine
After much fluffing around I managed to get Apache::Reload to work for .pm
files with:
httpd.conf
Location /
PerlRequire /the/path/to/the/perl/startup.pl
PerlInitHandler Apache::Reload
SetHandler perl-script
PerlHandler Apache::Registry
Options +ExecCGI
/Location
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
James wrote:
Thus spake Christoph Lange ([EMAIL PROTECTED]):
I am using use Apache::Reload; in a module but it does not work. I tell
my main-script where to find this module via use lib
'/home/path/for/modules'. Might this be the (or one) reason why
Apache::Reload does not work?
Do I have
Hi,
I am using "use Apache::Reload;" in a module but it
does not work. I tell my "main"-script where to find this module via "use lib
'/home/path/for/modules'". Might this be the (or one) reason why Apache::Reload
does not work?
Do I have to add t
Thus spake Christoph Lange ([EMAIL PROTECTED]):
I am using use Apache::Reload; in a module but it does not work. I tell
my main-script where to find this module via use lib
'/home/path/for/modules'. Might this be the (or one) reason why
Apache::Reload does not work?
Do I have to add
On Thu, 2 Aug 2001, Sidharth Malhotra wrote:
In the Apache::Reload module, if the 'require' fails, your script bails out,
and your client gets status 500. The side effect is that totally unrelated
scripts can fail because a bad programmer on another end of the system
forgot my a variable
On Thu, 2 Aug 2001, Sidharth Malhotra wrote:
SM In the Apache::Reload module, if the 'require' fails, your script
SM bails out, and your client gets status 500. The side effect is
SM that totally unrelated scripts can fail because a bad programmer
SM on another end of the system forgot my
::Reload???
On Tue, 31 Jul 2001, Bryan Coon wrote:
I must have missed something in setting up Apache::Reload. What I want is
simple that when I make a change in my scripts I dont have to restart the
Apache server...
I put
PerlInitHandler Apache::Reload
in my httpd.conf, and added 'use Apache
(/home/stas/myproject);
require MyTest;
Apache::Reload won't find this file, unless you alter @INC in
startup.pl:
startup.pl
--
use lib qw(/home/stas/myproject);
and restart the server
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,
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 is normal I
of all, you will want to turn off Apache::Reload during
production. All of those stat()'s will slow down your server speed
significantly, as the disk is kept busy for each request.
Secondly, how is it you view your logs? I have a window running tail -f
with a grep filter:
tail -f /var/log/httpd
I must have missed something in setting up Apache::Reload. What I want is
simple that when I make a change in my scripts I dont have to restart the
Apache server...
I put
PerlInitHandler Apache::Reload
in my httpd.conf, and added 'use Apache::Reload' to the modules that I want
to be reloaded
Apache::Reload works by performing a stat on every file in %INC and calling
require for all the files that changed. It's quite possible that some of
the files in %INC are using relative paths (often '.' is in @INC). So, Perl
was able to load the file originally because the initial 'use
On Tue, 31 Jul 2001, Kyle Oppenheim wrote:
Apache::Reload works by performing a stat on every file in %INC and calling
require for all the files that changed. It's quite possible that some of
the files in %INC are using relative paths (often '.' is in @INC). So, Perl
was able to load
-Original Message-
From: Kyle Oppenheim
To: [EMAIL PROTECTED]
Sent: 7/31/01 10:01 PM
Subject: RE: Apache::Reload???
Apache::Reload works by performing a stat on every file in %INC and
calling
require for all the files that changed. It's quite possible that some
of
the files in %INC
On Tue, 31 Jul 2001, Bryan Coon wrote:
I must have missed something in setting up Apache::Reload. What I want is
simple that when I make a change in my scripts I dont have to restart the
Apache server...
I put
PerlInitHandler Apache::Reload
in my httpd.conf, and added 'use Apache::Reload
On Tue, 31 Jul 2001, Philip Mak wrote:
On Tue, 31 Jul 2001, Kyle Oppenheim wrote:
Apache::Reload works by performing a stat on every file in %INC and calling
require for all the files that changed. It's quite possible that some of
the files in %INC are using relative paths (often
will take effect automatically? I
would rather not have to go into each file manually and put use
Apache::Reload.
Do I just put
PerlInitHandler Apache::Reload
in httpd.conf? Is there anything else that I have to do?
no (re-)?read the manpage. it's all there.
It's possible that Matt wants
.
In perldoc Apache::Reload, the DESCRIPTION has the following sections:
- StatINC Replacement
- Register Modules Implicitly
- Register Modules Explicitly
- Special Touch File
I just re-read it again and realized that StatINC Replacement is what I
wanted... although it wasn't obvious from just reading
--On 30/07/01 06:43 -0400 Philip Mak wrote:
In perldoc Apache::Reload, the DESCRIPTION has the following sections:
- StatINC Replacement
- Register Modules Implicitly
- Register Modules Explicitly
- Special Touch File
I just re-read it again and realized that StatINC Replacement is what
not have to go into each file manually and put use
Apache::Reload.
Do I just put
PerlInitHandler Apache::Reload
in httpd.conf? Is there anything else that I have to do?
Would Apache::Reload be helpful in the case where you have
multiple virtualhosts which each want their own @INC ?
I tried fixing this problem with a previous release, but gave up
when I realized the implication of all those use lib ()
directives in my modules.
If you think so, maybe you should
On Mon, 23 Apr 2001, [EMAIL PROTECTED] wrote:
Would Apache::Reload be helpful in the case where you have
multiple virtualhosts which each want their own @INC ?
I tried fixing this problem with a previous release, but gave up
when I realized the implication of all those use lib
On Mon, 23 Apr 2001, Matt Sergeant wrote:
On Mon, 23 Apr 2001, [EMAIL PROTECTED] wrote:
Would Apache::Reload be helpful in the case where you have
multiple virtualhosts which each want their own @INC ?
I tried fixing this problem with a previous release, but gave up
when I realized
This is a minor update as promised with some patches from a couple of
sources to help reload when "use lib" is in effect.
Let me know if it works (or doesn't) please.
--
Matt/
/||** Founder and CTO ** ** http://axkit.com/ **
//||** AxKit.com Ltd ** ** XML
Apache::Reload is a replacement for Apache::StatINC, with more features
and better debugging. Slated to replace Apache::StatINC in mod_perl 1.26.
Changes:
- Fix a warning under perl 5.6
--
Matt/
/||** Director and CTO **
//||** AxKit.com Ltd ** ** XML Application Serving
-Original Message-
From: Mark Doyle [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 15, 2000 4:06 PM
To: Jimi Thompson
Cc: [EMAIL PROTECTED]
Subject: Re: Apache::Reload and environment variables
On Friday, December 15, 2000, at 04:01 PM, Jimi Thompson wrote
/profile then you probably don't
need to do this (but it can't hurt, either - I do both)
I don't know specifically why Apache::Reload is causing this behavior, but
try the above and see if that clears things up...
Hmmm, I have been using this set up for years and never had
a problem
Greetings,
I tried using Apache::Reload:
PerlSetEnv ORACLE_HOME /oracle/app/oracle/product/8.0.3/
PerlModule Apache::DBI
[...]
PerlModule Apache::Reload
PerlInitHandler Apache::Reload
PerlSetVar ReloadAll Off
but when I do, the error log gets filled with
"ORACLE_HOME not set!"
Only
Mark,
If the variable ORACLE_HOME doesn't change why not just set it as an
environment variable outside the program and export it?
Mark Doyle wrote:
Greetings,
I tried using Apache::Reload:
PerlSetEnv ORACLE_HOME /oracle/app/oracle/product/8.0.3/
PerlModule Apache::DBI
Apache::Reload
PerlInitHandler Apache::Reload
PerlSetVar ReloadAll Off
That snippet is from my httpd.conf file - it is globally
defined there. Isn't that the same as what you are saying?
Cheers,
Mark
This latest release of Reload adds the ability to specify an entire
hierarchy of modules in the ReloadModules list, like so:
PerlSetVar ReloadModules "My::Foo My::Bar Foo::Bar::*"
which will reload all modules from Foo/Bar.pm to Foo/Bar/Blue/Far/Gear.pm
and so on.
--
Matt/
Fastnet Software
.
That's what PerlFreshRestart was written for. But as the current state
goes it's deprecated since many people has reported segfaults with it (at
least for those who has this problem). Otherwise it does just like what
you have described above, without any relation to Apac
ASP-Loader(
'/path/to/scripts/', '\.asp$|$other_pattern_match'
StatINC = 1,
%OtherConfigs
);
}
This will make your web site only change upon server
graceful restart, and saves some stat() calls.
The StatINC mechanism is similar to what is provided
by Apache::Reload and Apach
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
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?
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
parent
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
forked
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 you reload modules,
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_perl, and I'm curious
Passing this along from the mason list.
Original Message
Subject: [OT]Apache::Reload (was Re: [Mason]More "At The Forge" articles)
Date: 29 Aug 2000 10:59:35 +0400
From: [EMAIL PROTECTED] (Alexei V. Barantsev)
To: [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
D
On Tue, 29 Aug 2000, Barrie Slaymaker wrote:
Passing this along from the mason list.
Thanks, Dave already passed it on. I've fixed the bug - new release today.
Original Message
Subject: [OT]Apache::Reload (was Re: [Mason]More "At The Forge" articles)
Date: 2
Apache::Reload is a drop-in replacement for Apache::StatINC that does so
much more...
It provides two more options beyond StatINC. The first is a way that you
can register modules to be reloaded. To do this, simply add:
use Apache::Reload;
to your module and it will automatically be detected
, but I've changed that
to have a parameter for what files to reload and other things like
that. It would make a lot of sense to merge your reload and StatINC
I think, with an on/off switch for "old StatINC behavior", possibly
invoked by loading Apache::StatINC (which would load
Apache:
h for "old StatINC behavior", possibly
invoked by loading Apache::StatINC (which would load
Apache::Reload).
See 0.02, its now a fully fledged StatINC replacement along with the new
functionality.
--
Matt/
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XM
make StatINC a two-mode module. In one mode
it stats @INC, like its name suggests, and in another it only stats
modules that have use()'d it. I would have thought Apache::Reload would
then be a better name for it, overall. I also don't think these two bits
of functionality need to be in the same
, but is it
sensible? It would basically make StatINC a two-mode module. In one mode
it stats @INC, like its name suggests, and in another it only stats
modules that have use()'d it. I would have thought Apache::Reload would
then be a better name for it, overall.
That seems right - so perhaps it would be better
Matt Sergeant's message:
On Sat, 12 Aug 100, Ken Williams wrote:
That seems right - so perhaps it would be better to integrate the
StatINC functionality into Apache::Reload than the other way around.
If it's called Apache::Reload, then it might make sense to have a
directive like
The uploaded file
Apache-Reload-0.02.tar.gz
has entered CPAN as
file: $CPAN/authors/id/M/MS/MSERGEANT/Apache-Reload-0.02.tar.gz
size: 2284 bytes
md5: 37c950bd5b8ef3238d14be207766e651
No action is required on your part
Request entered by: MSERGEANT (Matt Sergeant)
Request entered
According to Matt Sergeant:
package Apache::Reload;
What I've always wanted along these lines is the ability
to load something in the parent process that would take
a list of directories where modules are always checked
and reloaded (for your local frequently changed scripts)
plus one
On Sat, 12 Aug 2000, Leslie Mikesell wrote:
According to Matt Sergeant:
package Apache::Reload;
What I've always wanted along these lines is the ability
to load something in the parent process that would take
a list of directories where modules are always checked
and reloaded
On Sat, 12 Aug 2000, Leslie Mikesell wrote:
According to Matt Sergeant:
package Apache::Reload;
What I've always wanted along these lines is the ability
to load something in the parent process that would take
a list of directories where modules are always checked
and reloaded
On Sat, 12 Aug 100, Ken Williams wrote:
That seems right - so perhaps it would be better to integrate the
StatINC functionality into Apache::Reload than the other way around.
If it's called Apache::Reload, then it might make sense to have a
directive like 'ReloadMode' that could be set
This dates back to discussions nearly a year ago now, from Randal's
initial Stonehenge::Reload, and Doug saying he'd like to see a more
generic Apache::Reload that got rid of the necessity to call reload_me in
your own code... Anyway, I needed this facility too, since I wanted
modules to be able
:[EMAIL PROTECTED]]
Sent: Friday, August 11, 2000 7:13 AM
To: [EMAIL PROTECTED]
Subject: RFC: Apache::Reload
This dates back to discussions nearly a year ago now, from Randal's
initial Stonehenge::Reload, and Doug saying he'd like to see a more
generic Apache::Reload that got rid
On Fri, 11 Aug 2000, Matt Sergeant wrote:
This dates back to discussions nearly a year ago now, from Randal's
initial Stonehenge::Reload, and Doug saying he'd like to see a more
generic Apache::Reload that got rid of the necessity to call reload_me in
your own code... Anyway, I needed
[EMAIL PROTECTED] (Matt Sergeant) wrote:
On Fri, 11 Aug 2000, Matt Sergeant wrote:
This dates back to discussions nearly a year ago now, from Randal's
initial Stonehenge::Reload, and Doug saying he'd like to see a more
generic Apache::Reload that got rid of the necessity to call reload_me
94 matches
Mail list logo
