From owner-freebsd-questions@FreeBSD.ORG Tue May 19 14:26:42 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 712A11065674 for ; Tue, 19 May 2009 14:26:42 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by mx1.freebsd.org (Postfix) with SMTP id 12EAC8FC0C for ; Tue, 19 May 2009 14:26:41 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from source ([209.85.216.199]) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKShLBoYZXy+3YeOXGmDjmTkEdppETbgRP@postini.com; Tue, 19 May 2009 07:26:42 PDT Received: by pxi37 with SMTP id 37so2444976pxi.11 for ; Tue, 19 May 2009 07:26:41 -0700 (PDT) Received: by 10.142.103.11 with SMTP id a11mr45727wfc.113.1242743201395; Tue, 19 May 2009 07:26:41 -0700 (PDT) Received: from localhost ([76.231.178.131]) by mx.google.com with ESMTPS id 32sm8683599wfc.34.2009.05.19.07.26.38 (version=SSLv3 cipher=RC4-MD5); Tue, 19 May 2009 07:26:39 -0700 (PDT) Date: Tue, 19 May 2009 07:26:37 -0700 (PDT) From: Peter Steele To: Chuck Swiger Message-ID: <31829573.1061242743193573.JavaMail.HALO$@halo> In-Reply-To: <45A2F58C-968F-47F7-90E3-1F84F0B122C9@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: #freebsd-questions Subject: Re: 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: Tue, 19 May 2009 14:26:43 -0000 >The pthread_* calls you are making aren't listed as being safe to run >within the context of a signal handler, and could cause a thread >waiting on that condition to be unblocked and start running. Please >see earlier comments about mixing threads and signal handlers. Okay, fair enough. I'll rework our signal handler logic to avoid using any calls that are not considered signal-safe. Better to be "safe" than sorry... :-) Thanks for the feedback.