Date: Wed, 29 Mar 2000 13:37:10 +0100 From: Ben Smithurst <ben@scientia.demon.co.uk> To: gerti-freebsds@bitart.com Cc: Alfred Perlstein <bright@wintelcom.net>, freebsd-stable@FreeBSD.ORG Subject: Re: Random signal 9 (SIGKILL), please help! Message-ID: <20000329133710.E96553@strontium.scientia.demon.co.uk> In-Reply-To: <20000329102024.3950.qmail@camelot.bitart.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > > However it will probably take some time before I can wrap my head > around that code, it's not exactly heavily commented... If anyone > with more intimate knowledge could have a look I'd appreciate that. Apparently syslogd could do this, I think a fix was commited recently, before RELENG_4 was branched, and it was fixed in RELENG_3 as well (possibly RELENG_2_2 even). -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000329133710.E96553>