From owner-freebsd-stable Tue Mar 28 20:11: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camelot.bitart.com (BITart-45.BITart.com [206.103.221.45]) by hub.freebsd.org (Postfix) with SMTP id 5E4AE37BFDC for ; Tue, 28 Mar 2000 20:11:01 -0800 (PST) (envelope-from gerti@bitart.com) Received: (qmail 3029 invoked by uid 101); 29 Mar 2000 04:11:04 -0000 Message-ID: <20000329041104.3028.qmail@camelot.bitart.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1) Received: by NeXT.Mailer (1.148) From: Gerd Knops Date: Tue, 28 Mar 2000 22:11:04 -0600 To: freebsd-stable@freebsd.org Subject: Random signal 9 (SIGKILL), please help! Reply-To: gerti-freebsds@BITart.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have a large software package running on a lot of machines and several Unixes. Only on the FreeBSD systems I see that child processes occasionaly get killed by a signal 9, and I just can't figure out why. Syslog does not give any indication. The machines do not swap (I know processes may get killed when the systems run out of swap space). The times at which the processes are killed does seem to be random, meaning it does not seem dome house keeping code that causes it. The processes are spawned from various daemons, and are killed at different points in their existence, even when just barely started and no resources to mention are consumed yet. All processes run as root, so 'limit' should not be the cause. Is there anything else but the swapper that can trigger a 'signal 9' to be sent to processes? The systems in question run a variety of versions, starting from 3.2 Release to a fairly recent (4 weeks) 3.4 stable. Any tips and ideas would be more than welcome. Thanks Gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message