-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay,
I've done some Googling and it does appear as if this could be the
source of this problem...
This page in particular suggests that:
http://www.pingle.org/2006/10/18/php-crashes-extensions/
However, I've tried all sorts of combinations wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any suggestions where I might start first in tweaking this file?
# cat /usr/local/etc/php/extensions.ini
extension=gettext.so
extension=mcrypt.so
extension=ftp.so
extension=session.so
extension=posix.so
extension=xml.so
extension=ctype.so
extension=r
Joe Auty wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just FYI, disabling eAccelerator hasn't rid me of this problem. I am
using PHP as an Apache module.
I might look at using Fast CGI, or else simply ignore this problem. Is
there a list somewhere of PHP apps that don't work with Fas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just FYI, disabling eAccelerator hasn't rid me of this problem. I am
using PHP as an Apache module.
I might look at using Fast CGI, or else simply ignore this problem.
Is there a list somewhere of PHP apps that don't work with Fast CGI,
or wil
Joe Auty wrote:
> I've also seen some info which suggests that this might be an Apache bug
> of some sort, but I've seen this in both Apache 1.3 and 2.0. Right now,
> I'm running 2.0.59 with eAccelerator.
>
> I guess the next step might be to try disabling eAccelerator... I'll let
> you know if t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Forgot to mention, I'm using Apache with the prefork MPM.
On Jan 20, 2007, at 5:16 AM, Joe Auty wrote:
Hello,
I've seen a lot of information on Google about this error message
I've been seeing a lot of in my logs:
pid 11443 (httpd), uid 80:
Hello,
I've seen a lot of information on Google about this error message
I've been seeing a lot of in my logs:
pid 11443 (httpd), uid 80: exited on signal 6
pid 11454 (httpd), uid 80: exited on signal 6
pid 11447 (httpd), uid 80: exited on signal 6
pid 11442 (httpd), uid 80: exited on signal
