From owner-freebsd-questions@FreeBSD.ORG Mon May 18 16:23:28 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24757106566C for ; Mon, 18 May 2009 16:23:28 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by mx1.freebsd.org (Postfix) with SMTP id BA7578FC1D for ; Mon, 18 May 2009 16:23:27 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from source ([209.85.198.241]) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKShGLf6BKvVSME6cHa+fXJWR5kmGwwM2G@postini.com; Mon, 18 May 2009 09:23:27 PDT Received: by rv-out-0708.google.com with SMTP id f25so1847421rvb.36 for ; Mon, 18 May 2009 09:23:26 -0700 (PDT) Received: by 10.141.211.8 with SMTP id n8mr2660766rvq.167.1242663806896; Mon, 18 May 2009 09:23:26 -0700 (PDT) Received: from localhost ([76.231.178.131]) by mx.google.com with ESMTPS id f21sm13692881rvb.5.2009.05.18.09.23.25 (version=SSLv3 cipher=RC4-MD5); Mon, 18 May 2009 09:23:26 -0700 (PDT) Date: Mon, 18 May 2009 09:23:22 -0700 (PDT) From: Peter Steele To: #freebsd-questions Message-ID: <7097313.721242663800853.JavaMail.HALO$@halo> In-Reply-To: <29027918.701242663578842.JavaMail.HALO$@halo> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Why would a kill -2 not work? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2009 16:23:28 -0000 Under what circumstances might a "kill -2 nnn" not work. I have a Python app with a signal handler configured to catch INT signals. It seems to work fine, but we've recently noticed that after the app has run for a while the kill -2 no longer works. This seems pretty suspicious, perhaps indicating our app is misbehaving in some way. What might cause the signal handler to stop working? Is there a better list for this question?