From owner-freebsd-questions Sun May 14 9: 5:35 2000 Delivered-To: freebsd-questions@freebsd.org Received: from aurora.scoop.co.nz (aurora.scoop.co.nz [203.96.152.68]) by hub.freebsd.org (Postfix) with ESMTP id 7CFF537B6A2 for ; Sun, 14 May 2000 09:05:31 -0700 (PDT) (envelope-from andrew@scoop.co.nz) Received: from localhost (localhost [127.0.0.1]) by aurora.scoop.co.nz (8.9.3/8.9.3) with SMTP id EAA04207 for ; Mon, 15 May 2000 04:05:27 +1200 (NZST) Date: Mon, 15 May 2000 04:05:27 +1200 (NZST) From: Andrew McNaughton Reply-To: andrew@scoop.co.nz To: freebsd-questions@freebsd.org Subject: What's killing my processes? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Something seems to be knocking off various processes on my server with the equivalent of a 'kill -9'. This has included processes run from the shell as root (make, pico) and some cron jobs. I'm guessing there's more, but those are the ones I have a little information on. The only thing I can think of that might do something like this is resource limits, but that seems unlikely to hit pico in mid use on a small file, and there's no apparent resource crunch going on. I think I can rule this out. Is there any other reason the kernel itself might issue KILL signals? How can I get information on what's going on? Is there some way I can put in a trace on any KILL signals issued on the system so I can identify the culprit process (or kernel)? I can get a list of killed processes from the system accounting (lastcomm), but I need the signal type and source. Any ideas? Andrew McNaughton -- Andrew McNaughton andrew@squiz.co.nz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message