Date: Sat, 18 Sep 2004 17:28:41 -0500 From: "Kevin D. Kinsey, DaleCo, S.P." <kdk@daleco.biz> To: Paul Schmehl <pauls@utdallas.edu> Cc: Vonleigh Simmons <nospam@illusionart.com> Subject: Re: Apache13 + mod_php segfault at startup Message-ID: <414CB699.3040606@daleco.biz> In-Reply-To: <07d501c49dbb$69a73ef0$7702a8c0@officeeagle> References: <CF42FFD9-090A-11D9-B42A-000A2791B6EC@illusionart.com> <07d501c49dbb$69a73ef0$7702a8c0@officeeagle>
index | next in thread | previous in thread | raw e-mail
Paul Schmehl wrote: >----- Original Message ----- >From: "Vonleigh Simmons" <nospam@illusionart.com> >To: <freebsd-questions@freebsd.org> >Sent: Friday, September 17, 2004 7:36 PM >Subject: Apache13 + mod_php segfault at startup > > >>Any suggestions at all are welcomed. I'm willing to try anything at >>this point. It was all working beautifully until I did a portupgrade of >>apache and mod_php. I really wish I would've just left it alone. >> >> >Did you read /usr/ports/UPDATING? The php port has changed. Now, you do a >base install, and then you install the extensions separately. And you have >to make sure to comment out the extensions_dir variable in your php.ini >file. > >I'd bet that's what your problem is. > > > Well, you might have to pony up the cash. As of last night, I've got both this issue and the portupgrade/ruby segfault messing with my mind. Matt Seaman had posted something about incompatible openssl libs; I'm currently trying a complete buildworld/installworld cycle. However, if commenting out the extensions dir in php.ini would help, I'm game to try; but when I did it, PHP complained it couldn't load its modules.... No flame intended, but something weird seems to be in the water this weekend... Kevin Kinseyhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?414CB699.3040606>