I built Apache from source (not from ports) and it runs great, except every once in a while in the dmesg output I get: pid 98142 (httpd), uid 65534: exited on signal 11 I don't know if it affects performance at all, and I haven't heard anyone complain, so I've just ignored it. I'm wondering if anyone else has had this quirk and if they know why it's causing it. I know signal 11 is usually a sign of bad memory or buggy hardware, but I am in no position now to replace any of it. So if that's the case, I'll just keep ignoring it until I get an upgrade... Thanks! Matt
At 11:53 AM 29/01/2004, Matt King wrote:>I built Apache from source (not from ports) and it runs great, except >every once in a while in the dmesg output I get: > >pid 98142 (httpd), uid 65534: exited on signal 11 > >I don't know if it affects performance at all, and I haven't heard anyone >complain, so I've just ignored it. I'm wondering if anyone else has had >this quirk and if they know why it's causing it. > >I know signal 11 is usually a sign of bad memory or buggy hardware,Or buggy software. eg. a cgi script like #include <stdio.h> int main(void) { char *t2; char t; t2= (char *) malloc(10); t = t2[40000]; return 0; } will cause the apache process running the script to die with a sig 11. Where you need to be careful of about hardware is in situations where known good programs are aborting randomly with sig 11s. eg. if you are getting random sig 11s when doing a buildworld. That is usually indicative of bad hardware. Take a look through your apache logs to see what is causing the sig 11. It might just be some buggy cgi script. ---Mike