Date: Fri, 29 Mar 2002 15:16:42 +0000 From: Nick Barnes <Nick.Barnes@pobox.com> To: "'freebsd-stable@freebsd.org'" <freebsd-stable@FreeBSD.ORG> Subject: Re: execl() after fork() in signal handler - strange things happen :) Message-ID: <33467.1017415002@thrush.ravenbrook.com> In-Reply-To: Message from =?koi8-r?Q?=E2=C5=D2=A3=DA=CB=CF_=E9=D7=C1=CE?= <iberiozko@infodom.ru> of "Fri, 29 Mar 2002 14:22:31 %2B0300." <3649F9FBD2621F4498A022E513C5CA2101528B@falcon.win.infodom.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33467.1017415002>