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 the path for my modules to @INC in
the
I've made some progress since my stupid and, admitedly, rather careless,
error with the upload_hook extended by libapreq. I finally gave up on
debugging it in it's current context and made a seperate light module setup
just to test. Currently, I'm using the Apache::Test::UploadMeter namespace
On Sun, 14 Oct 2001, Alexei Danchenkov wrote:
Hello, Randy and All,
I still can't compile mod_perl from source. I can compile other Perl modules
without problems, whether they are completely built on Perl or contain C/C#
modules (.xs). However, I still can't compile mod_perl with the same
I just noticed that Apache 1.3.22 is out. Details here:
http://www.apacheweek.com/issues/01-10-12
3 security patches included, plus enhancements to ab, mod_auth (now
understands FS permissions), and the manual, plus numerous other bits and
pieces.
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 the
Hello modperl,
I'm run into weird problem: apache output (HTTP headers and entity)
appears in the my own separate log file.
Here is scenario:
I'm fork a new process, cleanup for exec, redirect STD(IN|ERR|OUT)
in the /dev/null,/tmp/err,/tmp/out correspondingly, chdir '/' and
start
