-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> Well, it seems to be saying that it was terminated by SIGKILL which I > can't see a reason to be internally generated. Is there anything else > running on the system that might (for example) be taxing memory to cause > an OOM killing spree or some such? Yes, that is certainly possible. I've got some mod_perl kids that could potentially flare up when the site gets busy. I don't think that explains the one at 3:30 in the morning though, but I've reduced the number of kids and I'll see if that helps. So far, no more occurances since 16:15 EST. Thanks, - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200503282200 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFCSMUPvJuQZxSWSsgRAqwnAJ4lGO4ZBboE9xCbva6Wtk2b+MPOaACgxrA9 AoKz1mGOsf/L8pAy1+ybM4E= =zYYP -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
