I think that if mod_perl programs could be very well encrypted, this
technology would be a little more used than it is now, but they
can't, and
if this is a disadvantage for some of us, we shouldn't say that the
programmers shouldn't need such a thing.
Teddy makes a good point. This discussio
P.P.S
You might try being nicer to volunteers you are trying to help
you and not call them idiots.
I suspect the subject was meant to be read, "idiot's unsubscribe help
request", and not, "help me unsubscribe, idiots!"
- Danny
I have tested the problem with a barebones build of httpd on
FreeBSD 5 and 6. I do not believe any different library versions
are shared between this module and Apache or other loaded Apache
modules; symbol conflicts were my first thought.
No idea why... but I've definitely encountered that
I'm wondering if anyone can shed light on the circumstances of a segv
with httpd2.2.2/mod_perl2.0.2. The module being loaded in
Sleepycat::DbXml (part of the Sleepycat BDB XML distribution). The
segfault occurs upon Apache startup with either:
a) The module is loaded as use Sleepycat::DbX
On Feb 24, 2006, at 4:00 PM, Alan Bailward wrote:
It probably really comes down to personal preference and
familiarity FWIW.
And marketing.
