From owner-freebsd-stable Wed Mar 29 5:31:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id E5EA637B726 for ; Wed, 29 Mar 2000 05:31:49 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 29 Mar 2000 14:31:48 +0100 (BST) Date: Wed, 29 Mar 2000 14:31:48 +0100 From: David Malone To: gerti-freebsds@bitart.com Cc: Alfred Perlstein , freebsd-stable@FreeBSD.ORG Subject: Re: Random signal 9 (SIGKILL), please help! Message-ID: <20000329143148.A25616@walton.maths.tcd.ie> References: <20000329041104.3028.qmail@camelot.bitart.com> <20000328204948.K21029@fw.wintelcom.net> <20000329043747.3094.qmail@camelot.bitart.com> <20000328213754.L21029@fw.wintelcom.net> <20000329102024.3950.qmail@camelot.bitart.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000329102024.3950.qmail@camelot.bitart.com>; from gerti@bitart.com on Wed, Mar 29, 2000 at 04:20:24AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 29, 2000 at 04:20:24AM -0600, Gerd Knops wrote: > I think I found a correlation between pid roll over (from 99999 > to 0) and the spurious signals. Some program seems to keep > taps on pids that already went away, and when they 'come back' they > are killed again. I am suspicious of syslogd at the moment (I pipe > syslog output through a filter), one of the very few programs in the > base system that are running on those systems and that uses SIGKILL. You could try doing: ktrace -t s -p $pid on syslogd and then checking to see if the signals it sends corrisponds to the SIGKILL your processes get. (Providing you have times for them). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message