-Original Message-
From: David Veatch [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 19, 2000 11:48 AM
To: [EMAIL PROTECTED]
Subject: PerlFreshRestart Question/Problem
Greetings,
[i sent this once, but think it got hung up at the mail server... my
apologies if this already
At 01:22 PM 5/19/00 -0400, Geoffrey Young wrote:
I think the title says it best:
http://perl.apache.org/guide/troubleshooting.html#Evil_things_might_happen
_when_us
Sweet. Thanks. So the problem is probably any number of weak module
issues. That's enough for me right now... turning it off
At 01:22 PM 5/19/00 -0400, Geoffrey Young wrote:
I think the title says it best:
http://perl.apache.org/guide/troubleshooting.html#Evil_things_might_happen
_when_us
Sweet. Thanks. So the problem is probably any number of weak module
issues. That's enough for me right now... turning
"SB" == Stas Bekman [EMAIL PROTECTED] writes:
SB Huh? Wasn't the mod_perl 1.23 supposed to fix this problem with DSO? I
SB thought to remove this item from the Guide. Are there still problems with
SB DSO?
DSO works great for me now with the fixes in place of mod_perl 1.23.
However, note that
On Fri, 19 May 2000, Stas Bekman wrote:
Huh? Wasn't the mod_perl 1.23 supposed to fix this problem with DSO? I
thought to remove this item from the Guide. Are there still problems with
DSO?
If I remember correctly the problem was of broken internal pointers when
the DSO code was reloaded.
On Fri, 19 May 2000, Doug MacEachern wrote:
On Fri, 19 May 2000, Stas Bekman wrote:
Huh? Wasn't the mod_perl 1.23 supposed to fix this problem with DSO? I
thought to remove this item from the Guide. Are there still problems with
DSO?
If I remember correctly the problem was of
: PerlFreshRestart Question/Problem
At 01:22 PM 5/19/00 -0400, Geoffrey Young wrote:
I think the title says it best:
http://perl.apache.org/guide/troubleshooting.html#Evil_things_might_happen
_when_us
Sweet. Thanks. So the problem is probably any number of weak module
issues. That's
