* Perrin Harkins [EMAIL PROTECTED] [2002-12-30 19:07]:
Explanations and other suggested approaches to handling this problem
will be most welcome.
My suggestion in the past has been to PerlRequire a startup.pl that
does a use on your modules, instead of pulling them in with
PerlModule.
I
David Wheeler wrote:
Hi All,
I'm developing a new module for mod_perl 1.27, and I'm noticing that
some code is getting executed twice when the Apache server starts up.
It was supposed to be fixed in 1.25_01:
=item 1.25_01 - July 6, 2001
...
fix double-loading bug of Perl{Require,Module}s at
On Monday, December 30, 2002, at 02:45 PM, Stas Bekman wrote:
David Wheeler wrote:
Hi All,
I'm developing a new module for mod_perl 1.27, and I'm noticing that
some code is getting executed twice when the Apache server starts up.
It was supposed to be fixed in 1.25_01:
=item 1.25_01 - July
David Wheeler wrote:
On Monday, December 30, 2002, at 02:45 PM, Stas Bekman wrote:
David Wheeler wrote:
Hi All,
I'm developing a new module for mod_perl 1.27, and I'm noticing that
some code is getting executed twice when the Apache server starts up.
It was supposed to be fixed in
Is anyone getting duplicates (i.e. 2 of the same email) of this thread? It just
started happening today.
Brian
-Original Message-
From: Stas Bekman [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 30, 2002 5:06 PM
To: David Wheeler
Cc: [EMAIL PROTECTED]
Subject: Re: Modules Executed
Hann, Brian wrote:
Is anyone getting duplicates (i.e. 2 of the same email) of this thread? It just started happening today.
I can't tell, since I never receive dups because of the procmail rule:
:0 Wh: msgid.lock
| formail -D 8192 saved/msgid.cache
hint, hint ;)
Explanations and other suggested approaches to handling this problem
will be most welcome.
My suggestion in the past has been to PerlRequire a startup.pl that does a
use on your modules, instead of pulling them in with PerlModule.
Of course, if you turn PerlFreshRestart on then this is the
On Monday, December 30, 2002, at 04:09 PM, Perrin Harkins wrote:
My suggestion in the past has been to PerlRequire a startup.pl that
does a
use on your modules, instead of pulling them in with PerlModule.
Of course, if you turn PerlFreshRestart on then this is the intended
behavior.
That's
