On Sat, 10 Feb 2001, Brian Aker wrote:
> Ok, are you adding in any modules dynamically? Say PHP
> or any mysql ones?
LoadModule dav_module libexec/libdav.so
LoadModule mysql_auth_module libexec/mod_auth_mysql.so
LoadModule throttle_module libexec/mod_throttle.so
...but as far as I can tell, they worked fine with slash 1.0.9. Is there
an issue with dynamically loaded modules that I should be aware of?
I think maybe what I should do next is:
- rebuild apache with 1.3.17, all the latest stuff. This doesn't thrill
me, but I know I have to do it evenutually. I've been roughly following
the apache recipe at <http://www.delouw.ch/linux/apache.phtml>, through
step 6 or so (plus mod_auth_mysql). I'd been avoiding PHP because of
PHP/mod_perl conflicts, but I understand those are resolved now, so I
might try adding it back in.
- go through the include list and be sure that the latest versions of the
various Perl modules are really there.
This is a longshot, but I know that the various XML modules and expat
libraries have caused me a *lot* of problems on other machines and
installs; XML::Parser 2.30 introduced the use of the external expat
library, and when I used it with mod_perl I had no end of trouble. I had
to back down to 2.28 to keep things stable, but apache would segfault
rather randomly untli I did that, and that's what I attributed it to.
The documentation I could find on that was pretty sketchy, but it appeared
to be a mod_perl/expat conflict of some sort. Maybe it's better now?
Is there anything else I can do on this build to help figure out what's
going wrong? Would running a trace on apache do it? The segfault is
easily reproducible in this case - load the page with the user handler
active and it segfaults. I did an apache trace once before, but I'd have
to see if I can remember how to do it - I'm not an apache/kernel
hacker. But if it would help, I'm happy to do it.
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
Be kind. Remember, everyone you meet is fighting a hard battle.