On Thu, 11 Apr 2002 10:05:46 -0400 (EDT), Chris Devers wrote: > But isn't it supposed to not work unless it offers error messages?
You would think so, but there are no error messages pertaining to a problem. And Apache ends up not running. I think that is the most disturbing thing. > It's only a partial remedy, but are your mod_perl related config statments > wrapped in an appropriate <if...> block? > > <IfModule mod_perl.c> > PerlSendHeader On > PerlHandler Apache::Registry > AddHandler perl-script .mpl > </IfModule> Well, the thing is, I don't think it even gets that far in executing the conf file. In my case, I'm suspecting that something in the current mod_perl installation was conflicting with the perl 5.6.1. Although, this is generally a cleaner design of the conf file, it isn't helpful in this case. The LoadModule line seems to make Apache abort startup altogether. > and maybe sign up for -- the mod_perl list. Chances are this is a general > mod_perl issue, as opposed to a specific MacOSX issue. See lists.perl.org > and, specifically (but among others) the mod_perl users' list at > http://lists.perl.org/showlist.cgi?name=modperl-user Possibly, although I'm suspecting this is something just with OS X. I am wondering if the mod_perl library was reinstalled with the new Apache (probably), which had some dynamic linking done, designed for perl 5.6.0 (or possibly vice-versa), and the updated copy got "out of sync" with the newer perl. I spent a lot of time looking into this, in several other sites, several web searched, and a couple lists. *shrug* Definitely not something that seems to occur very often, except to Puneet and I. heh. -Alex ================================================== Email: [EMAIL PROTECTED] Website: http://www.beardeddragon.org/ ==================================================
