perl_destruct/perl_free are not called at restart, only during child_exit.
it looks like that might need to change to finish the dso puzzle. I
experienced some problems there, but that was a few years ago, looks
like it's time to revisit.
But it is called when Apache unloads the modules
Doug MacEachern wrote:
wow, *nice* catch!! Daniel, I can't thank you and Alan enough for your
efforts here. it's such a thorny problem to debug, the closest I came was
trying to prevent the dlclose of modperl's libperl.so, but had no idea why
that bandaid prevented the bleeding. I hadn't
Seems correct to me, although as I said before the patch should really
go in DynaLoader - after all it is conceivable that perl embedders other
than Apache could be hit by this problem.
Yes, I agree, but this will not before perl 5.006 and much people are still
using perl 5.004...
Gerald
perl_destruct/perl_free are not called at restart, only
during child_exit.
it looks like that might need to change to finish the dso puzzle. I
experienced some problems there, but that was a few years ago, looks
like it's time to revisit.
But it is called when Apache
Gerald Richter wrote:
Seems correct to me, although as I said before the patch should really
go in DynaLoader - after all it is conceivable that perl embedders other
than Apache could be hit by this problem.
Yes, I agree, but this will not before perl 5.006 and much people are still
On Tue, Jan 18, 2000 at 11:02:27PM -0800, Doug MacEachern wrote:
On Sat, 15 Jan 2000, Daniel Jacobowitz wrote:
...
Notice that DBI is never dlclose()'d. But mod_perl is, when apache
unloads its modules. The linker is not clever enough to realize that
DBI depends on symbols in
Daniel Jacobowitz [EMAIL PROTECTED] writes:
This worked! Can I get opinions on the attached patch?
I am not competent to check whether the patch has any hidden problems,
but I hope Doug will be able to evaluate it and include it in the next
release. Your description of the sequence leading up
"Frank D. Cringle" wrote:
Daniel Jacobowitz [EMAIL PROTECTED] writes:
This worked! Can I get opinions on the attached patch?
I am not competent to check whether the patch has any hidden problems,
but I hope Doug will be able to evaluate it and include it in the next
release. Your
