From owner-freebsd-stable Fri Mar 29 7:16:17 2002 Delivered-To: freebsd-stable@freebsd.org Received: from raven.ravenbrook.com (raven.ravenbrook.com [193.82.131.18]) by hub.freebsd.org (Postfix) with ESMTP id D62DC37B41D for ; Fri, 29 Mar 2002 07:16:13 -0800 (PST) Received: from thrush.ravenbrook.com (thrush.ravenbrook.com [193.112.141.249]) by raven.ravenbrook.com (8.11.6/8.11.6) with ESMTP id g2TFGBO79750 for ; Fri, 29 Mar 2002 15:16:11 GMT (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (localhost [127.0.0.1]) by thrush.ravenbrook.com (8.11.6/8.11.6) with ESMTP id g2TFGgK33470 for ; Fri, 29 Mar 2002 15:16:42 GMT (envelope-from nb@thrush.ravenbrook.com) From: Nick Barnes To: "'freebsd-stable@freebsd.org'" Subject: Re: execl() after fork() in signal handler - strange things happen :) In-Reply-To: Message from =?koi8-r?Q?=E2=C5=D2=A3=DA=CB=CF_=E9=D7=C1=CE?= of "Fri, 29 Mar 2002 14:22:31 +0300." <3649F9FBD2621F4498A022E513C5CA2101528B@falcon.win.infodom.ru> Date: Fri, 29 Mar 2002 15:16:42 +0000 Message-ID: <33467.1017415002@thrush.ravenbrook.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've taken this over to -questions (the answer is: the signal is blocked in the handler, and that mask is inherited by first the child and then the execl'd process, so of course the new process can't see SIGHUP). Nick Barnes Ravenbrook Limited To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message