The Salisburys wrote:
I experienced some very bizarre and unexpected behaviour with Apache
and mod_perl when I loaded mod_perl dynamically as above. Then I
discovered
that the httpd I was using had mod_perl linked statically. Everything
cleared up when I removed the dynamic load.
Good point
how does one know whats in a RPM package :apache-1.3.27-4.i386.rpm
is mod_perl built in the one below
I cannot answer that question.
But I can suggest the following: get the Apache (httpd) up running
*without* dynamically loading mod_perl and see if it works.
Also, try th e-l option on httpd, which lists the compiled-in modules.
Finally, perhaps examine the strings out on the httpd file ... it
may indicate the presence or absence of mod_perl.
cheers
rickw
--
_________________________________
Rick Welykochy || Praxis Services
For years, Microsoft has had a policy of announcing products that don't
exist yet, to cause customers to stop buying a competitor's product.
That's Vapourware. Is it really any shock that they would want to prevent
customers from using more robust OSs and tools, by offering Vapoursecurity?
-- David Maxwell on Full Disclosure
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
