From owner-freebsd-questions@FreeBSD.ORG Fri Sep 14 20:55:42 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3037D16A418 for ; Fri, 14 Sep 2007 20:55:42 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (66-230-99-27-cdsl-rb1.nwc.acsalaska.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 04AE013C457 for ; Fri, 14 Sep 2007 20:55:41 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id 8841D1CC97 for ; Fri, 14 Sep 2007 12:55:40 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org Date: Fri, 14 Sep 2007 22:55:38 +0200 User-Agent: KMail/1.9.7 References: <0b9d01c7f6f1$6ecedb30$6400a8c0@msdi.local> <46EAF373.3000903@ibctech.ca> In-Reply-To: <46EAF373.3000903@ibctech.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709142255.39515.fbsd.questions@rachie.is-a-geek.net> Subject: Re: kernel log messages X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2007 20:55:42 -0000 On Friday 14 September 2007 22:47:47 Steve Bertrand wrote: > > +pid 85092 (httpd), uid 80: exited on signal 11 pid 85097 (httpd), uid > > > > +80: exited on signal 11 pid 85099 (httpd), uid 80: exited on signal 11 > > > > Is this something I should care about ? First time I see this, and since > > the os mention it to me, I guess it's something important :-) > > In almost every case I've seen posted to this list regarding sig 11 > problems, the response has nearly always been replace memory. > > Even in a case of my own a few years back, said recommendation fixed my > problem. (I think mine was during a buildworld). > > Aside from that, I've also heard of heat (as already stated this > thread), and flaky power supply. While this may be true, 90% of the cases of SIGSEV is programming error, combine that with a publically accessible daemon, it means unauthorized access thread. This is why it's listed in daily and why running the suggested portaudit is a good idea (both apache and php released security releases this week FYI). -- Mel