From owner-freebsd-threads@FreeBSD.ORG Mon Jun 21 05:41:22 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEDC016A4CE for ; Mon, 21 Jun 2004 05:41:22 +0000 (GMT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEEB643D54 for ; Mon, 21 Jun 2004 05:41:22 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 28EFDFD067; Sun, 20 Jun 2004 22:41:22 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25599-07; Sun, 20 Jun 2004 22:41:21 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id A5DF2FD04C; Sun, 20 Jun 2004 22:41:21 -0700 (PDT) From: Sean McNeil To: Koryn Grant In-Reply-To: References: <1087794678.46146.4.camel@server.mcneil.com> Content-Type: text/plain Message-Id: <1087796481.46307.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 20 Jun 2004 22:41:21 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-threads@freebsd.org Subject: Re: kill(pid,0) sends a signal or not? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2004 05:41:22 -0000 On Sun, 2004-06-20 at 22:26, Koryn Grant wrote: > On Sun, 20 Jun 2004, Sean McNeil wrote: > > > Any info on how threads are suppose to behave when a process does a > > kill(pid,0) would be greatly appreciated. > > The Single Unix Specification speaks thusly about kill(): > > "If sig is 0 (the null signal), error checking is performed but no signal is > actually sent. The null signal can be used to check the validity of pid." Thanks, Koryn. It looks like what I'm seeing with the 0 value is how kse/pthread is waking up another thread through signalcontext. All looks legit. I thought that it was getting there from a kill(). Cheers, Sean