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 -Mlib=/home/bruce/public_html/ffbal
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 und
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
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 work
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 pe
Stas Bekman wrote:
Harry Danilevsky wrote:
I did send the patch to Matt couple of days ago, but haven't heard
back yet.
Matt is on vacation
I suppose I can also brace myslef, add namespaces, and clean up my own
code.
That's a good idea.
As for the versioning, if this patch could be use
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 i
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
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 @I
* 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
Harry Danilevsky wrote:
> I did send the patch to Matt couple of days ago, but haven't heard back
> yet.
Matt is on vacation
> I suppose I can also brace myslef, add namespaces, and clean up my own
> code.
That's a good idea.
> As for the versioning, if this patch could be useful in both mod
I did send the patch to Matt couple of days ago, but haven't heard back yet.
I suppose I can also brace myslef, add namespaces, and clean up my own code.
As for the versioning, if this patch could be useful in both mod_perl
1.* and 2.0,
can it be applied to both distributions? I don't quite und
Harry Danilevsky wrote:
> I certainly agree with attaching a common prefix to a library, but what
> if I am already dealing
> with a bunch of modules written without prefix, and enough application
> code using those packages ?
> I suppose I could change the code, or alias names in symbol table,
I certainly agree with attaching a common prefix to a library, but what
if I am already dealing
with a bunch of modules written without prefix, and enough application
code using those packages ?
I suppose I could change the code, or alias names in symbol table, or do
some other trick;
I just fi
Harry Danilevsky wrote:
> Two reasons :
>
> 1. My site-specific modules don't necessarily have a common namespace
> (or even several namespaces);
> they just all live in /site/lib. Without a ReloadDirectories-like filter
> every time I add another module,
> say, /site/lib/Reports.pm I'll need
Two reasons :
1. My site-specific modules don't necessarily have a common namespace
(or even several namespaces);
they just all live in /site/lib. Without a ReloadDirectories-like filter
every time I add another module,
say, /site/lib/Reports.pm I'll need to add Reports to ReloadModules, and
[...]
> 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::*"
> 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
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 w
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
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 a
That worked :) Ahh, at least I solved ONE problem!
Thanks!
Bryan
> The solution is to extend @INC at the server startup to include
> directories you load the files from which aren't in @INC.
>
> For example, if you have a script which loads MyTest.pm from
> /home/stas/myproject:
>
> use lib
Does that work under Unix only? I am on NT and it does not appear to work.
Can someone clarify.
Thanks
Scott
-Original Message-
From: Stas Bekman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 31, 2001 9:38 PM
To: Bryan Coon
Cc: Matt Sergeant; '[EMAIL PROTECTED]'
Subject:
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::Re
>-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 poss
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' or 'requ
On Monday, December 18, 2000, at 09:23 AM, Geoffrey Young wrote:
> well, it's not the same - what he means is for you to export ORACLE_HOME in
> /etc/passwd or somesuch
>
> DBD::Oracle needs ORACLE_HOME set at compile time - for Registry scripts its
> ok to PerlSetEnv so that when your .cg
> -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
On Friday, December 15, 2000, at 04:01 PM, Jimi Thompson wrote:
> If the variable ORACLE_HOME doesn't change why not just set it as an
> environment variable outside the program and export it?
>> PerlSetEnv ORACLE_HOME /oracle/app/oracle/product/8.0.3/
>> PerlModule Apache::DBI
>> [...]
>> Pe
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
> [...]
>
Greg Stark wrote:
>
> Stas Bekman <[EMAIL PROTECTED]> writes:
>
> > But adds an additional stat() call for each request, which might be not
> > desired for "some" sites... I know it's quite fast. See:
> >
>http://thingy.kcilink.com/modperlguide/performance/Reducing_the_Number_of_stat_Ca.html
>
> Stas Bekman <[EMAIL PROTECTED]> writes:
>
> > But adds an additional stat() call for each request, which might be not
> > desired for "some" sites... I know it's quite fast. See:
> >
>http://thingy.kcilink.com/modperlguide/performance/Reducing_the_Number_of_stat_Ca.html
> >
> > But, yeah it's
Stas Bekman <[EMAIL PROTECTED]> writes:
> But adds an additional stat() call for each request, which might be not
> desired for "some" sites... I know it's quite fast. See:
>
>http://thingy.kcilink.com/modperlguide/performance/Reducing_the_Number_of_stat_Ca.html
>
> But, yeah it's cool!
In pr
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: 29 Aug 20
you may have missed the conversation yesterday on modperl-dev, but just to
recap...
it just came up that Apache::Symbol::undef_functions really isn't needed any
more. That is, 5.004+ avoids the manditory 'subroutine redefined' warnings
and makes then not-manditory. Thus local $^W stops the warn
36 matches
Mail list logo
