Howdy folks... got a wierd one here, although I bet someone knows what
to do about it.
I am running Apache 1.3.20, mod_perl 1.26, and mod_ssl (most recent
version that works with Apache 1.3.20). The following happens with Perl
5.005_03 and 5.6.1.
In my httpd.conf, I have :
# mod_perl stuff...
#
PerlRequire conf/startup.pl
PerlFreshRestart On
PerlModule Apache::LogFile
PerlLogFile logs/PTW-access.log PTW::access
PerlLogFile logs/PTW-error.log PTW::error
PerlLogFile logs/PTW-debug.log PTW::debug
PerlLogFile logs/PTW-security.log PTW::security
<Location /PTW-Server/FileFilter>
SetHandler perl-script
PerlHandler PTW::FileFilter
</Location>
So I have FileFilter.pm, which does some things, and is working quite
happily. On 4 of my other servers, I have this exact same configuration
with Apache 1.3.14 and mod_perl of similar vintage. My problem is that
my PerlHandler's (like PTW::FileFilter) cannot write to the log files.
I have been using statements like:
print PTW::error ("you had a big old error");
For some reason, with the updated config, this no longer works, and my
Apache error_log says:
Invalid command 'PerlLogFile' perhaps misspelled .... yadi yada.
Any clues why this would be any different in newer versions?
Also, I tried changing "PerlModule Apache::LogFile" to "PerlRequire
Apache::LogFile", which results in Apache barfing saying that there is
no such animal in @INC. I have verified that it is infact in the @INC
path, so why can Apache not see it?
Lastly, the very odd thing to me, is that something is successfully
creating the logs/PTW-access.log etc. If it can create them, how come I
cant write to them? Something is screwy, and I clearly do not have a
good grasp on what is going on. Can someone please help me a bit?
Thanks!
-Bryan
--
Bryan T. Schmidt
Systems/Network Administrator
Profitool Inc.
[EMAIL PROTECTED]
