From owner-freebsd-questions Mon Mar 27 14:21: 0 2000 Delivered-To: freebsd-questions@freebsd.org Received: from camelot.bitart.com (BITart-45.BITart.com [206.103.221.45]) by hub.freebsd.org (Postfix) with SMTP id 7940937BD35 for ; Mon, 27 Mar 2000 14:20:52 -0800 (PST) (envelope-from gerti@bitart.com) Received: (qmail 27488 invoked by uid 101); 27 Mar 2000 22:20:47 -0000 Message-ID: <20000327222047.27487.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: Mon, 27 Mar 2000 16:20:47 -0600 To: FreeBSD Questions Subject: Spurious SIGKILLs on FreeBSD 3.2 - 3.4 Reply-To: gerti@BITart.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have a large application written in perl that runs on several FreeBSD systems (anything from 3.2 release to 3.4 stable), as well as on some NEXTSTEP systems. The perl application spawns a number of children. My problem is that on the FreeBSD systems some of those children occasionally get killed (signal 9). The application/children run as root, and the systems have plenty of memory (no swapping at all). Syslog does not show anything unusual. No other users are logged in on those systems. The children are killed in various stages (idle, in the middle of I/O etc). Anyone have an idea what could cause those signals? Thankful for any tips Gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message