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
On Wed, 22 Aug 2001, Matt Sergeant wrote:
-Original Message-
From: Michael Styer [mailto:[EMAIL PROTECTED]]
In Makefile.PL I have:
snip abbreviated makefile code listing
I'm assuming you have more than that... :-)
Yes. :)
It actually looks like this:
package
-Original Message-
From: Michael Styer [mailto:[EMAIL PROTECTED]]
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.
:-)
In Makefile.PL I have:
package ConfigModule;
## ... (as
-Original Message-
From: Michael Styer [mailto:[EMAIL PROTECTED]]
That's because ConfigModule.pm isn't loaded at the time.
You'd have to
require() it or use() it.
Even when the makefile is declared as 'package ConfigModule;'
initally?
It seems strange that I would need to
I'll look into it, but my sysadmins are worried that
upgrading is going to
break, in strange and obscure ways, the multiple live
commercial sites we
have running on our servers. Are there any resources
available I might be
able to use to reassure them?
No! They have every right
-Original Message-
From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 6:41 AM
To: 'Michael Styer'; Matt Sergeant
Cc: [EMAIL PROTECTED]
Subject: RE: More problems with custom config directives (LONG)
[snip]
I'll look into it, but my sysadmins
On Wed, 22 Aug 2001, Matt Sergeant wrote:
OK, can you describe the problem a little more clearly? The Testing user
file bit doesn't seem to come from anywhere - any ideas where it's coming
from???
I had assumed it was coming from Apache, but your question made me
suspicious. After a little
Don't worry, it's all happening on an isolated development
server, I was
just wondering whether there are any resources that indicate
what things
might break when upgrading from 1.23 to 1.24. But if I can't get this
working soon time pressure will force me to use the
functional but
another source of documentation that I
know about (yet ;)
HTH
--Geoff
-Original Message-
From: brian moseley
To: [EMAIL PROTECTED]
Sent: 7/14/01 2:19 AM
Subject: custom config directives
is there any good thorough documentation on building custom
config directives other than what's
is there any good thorough documentation on building custom
config directives other than what's in the eagle book? i
left mine back in au and i don't really want to buy another
one :)
You're in luck, that chapter is on-line:
http://www.modperl.com/book/chapters/ch8.html
is there any good thorough documentation on building custom
config directives other than what's in the eagle book? i
left mine back in au and i don't really want to buy another
one :)
And the really GOOD NEWS!!! When I upgraded to mod_perl 1.24, the problem
went away. It all works like it's suppossed to now.
--On 06/09/00 12:02:40 -0700 Doug MacEachern [EMAIL PROTECTED] wrote:
On Thu, 8 Jun 2000, Rob Tanner wrote:
MirrorWiseKeyFile', perhaps mis-spelled or defined
On Thu, 8 Jun 2000, Rob Tanner wrote:
MirrorWiseKeyFile', perhaps mis-spelled or defined by a module not
included in the server configuration
...
PerlModule Apache::MirrorWise
this is becoming a common problem, try this bandaid, instead of that
PerlModule line:
Perl
delete
Hi All,
(This message is VERY long --I'm trying to include as much information as I
can)
Back on June 3 I posted a message about a problem I was having installing
custom configuration directives. Since then, I have been going over
everything with a fine tooth comb -- which was probably not
I cannot seem to get custom configuration directives to work in
apache (1.3.11) modperl (1.21). I would presume the examples in the
book do not work either. I found someone having similar problems
in the list archives, to which Doug provided a workaround which also
does not work.
Any
Eric Cholet [EMAIL PROTECTED] writes:
Perl
require Apache::TestDirective;
delete $INC{'Apache/TestDirective.pm'};
/Perl
#PerlModule Apache::TestDirective
Why are you using 'require', and not the PerlModule line you commented
out?
It appeared to work. =)
In searching the mail archives I
Following up to myself I am.
Firstly, that was Directive3 (not Directive4). Directive3 returns
OK.
$ bin/apachectl configtest
works just fine, no problems.
$ bin/apachectl start
is where it fails to find the command, looks like in some related
child process. It seems to be that the
I cannot seem to get custom configuration directives to work in
apache (1.3.11) modperl (1.21). I would presume the examples in the
book do not work either. I found someone having similar problems
in the list archives, to which Doug provided a workaround which also
does not work.
Any advice
18 matches
Mail list logo