From owner-freebsd-current Tue Dec 1 07:03:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06695 for freebsd-current-outgoing; Tue, 1 Dec 1998 07:03:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06690 for ; Tue, 1 Dec 1998 07:03:01 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id KAA16461; Tue, 1 Dec 1998 10:02:40 -0500 (EST) Date: Tue, 1 Dec 1998 10:02:40 -0500 (EST) From: John Fieber To: The Hermit Hacker cc: garman@earthling.net, freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Dec 1998, The Hermit Hacker wrote: > Unsure of when it started, but dmesg just gives line after line of: > > pid 7913 (httpd), uid 65534: exited on signal 11 > pid 7912 (httpd), uid 65534: exited on signal 11 > pid 7910 (httpd), uid 65534: exited on signal 11 > pid 7906 (httpd), uid 65534: exited on signal 11 > > Not thinking it was related until ppl brought up the 'daemon dying' > thread, I didn't mention it previously, but I killed off httpd and > restarted it, which stop'd the scrolling messages...but has not stop'd > thee 'junk pointer' messages... That is consistent with my dying daemons experience, but the you don't appear to have the swap space pressure that seems to trigger it for most other people. I've been saving all messages on the dying daemons topic and could email you the whole bundle if you like. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message