> -----Original Message-----
> From: Michael Styer [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 22, 2001 6:12 AM
> To: [EMAIL PROTECTED]
> Subject: More problems with custom config directives (LONG)
>
>
> Hi there,
>
> I'm another person in the short but persistent line of people
> who can't
> seem to get custom configuration directives to work.
>
> I'm working with the Eagle book on this, and I've read all
> the relevant
> threads I can find in the list archives, but since I'm having
> a slightly
> different problem from the one my fellow strugglers were having, the
> advice given to them didn't work for me.
>
> The symptom:
>
> On starting httpd, I get this response:
>
> Testing user file: NewConfigDirective
> argumentToDirective
>
> I tried doing away with the PerlModule directive and using
> the workaround
> suggested by Doug MacEachern on June 9 2000, which was to put these
> statements in the conf file:
>
> <Perl>
> delete $INC{'/path/to/ConfigModule.pm'};
> require ConfigModule;
> </Perl>
be aware that if you upgrade your mod_perl (as Matt suggested in a later
message) that this approach won't likely work anymore
see Doug's response to my question here
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=98863138232675&w=2
HTH
--Geoff