From owner-freebsd-hackers Wed Feb 20 10:40:33 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 38FE337B419 for ; Wed, 20 Feb 2002 10:40:19 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020220184017.OKUM1214.rwcrmhc54.attbi.com@InterJet.elischer.org>; Wed, 20 Feb 2002 18:40:17 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA63373; Wed, 20 Feb 2002 10:20:53 -0800 (PST) Date: Wed, 20 Feb 2002 10:20:52 -0800 (PST) From: Julian Elischer To: Jonathan BENSAMOUN Cc: hackers@freebsd.org Subject: Re: fork & launch In-Reply-To: <000501c1ba26$9d7727c0$2d2ae30a@johnport> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 1/ can you say whay you want to do this? 2/ check the code that creates kernel threads, (kthread_create()) On Wed, 20 Feb 2002, Jonathan BENSAMOUN wrote: > Hi > I coded a syscall which fork inside kernel and launch a new process. > The unique problem I got is when the father is waiting the child process > and received a sigkill signal. It freezes the system like a while (1) in > kernel mode. > Note that a sigkill to the child process does not matter at all. > It ts when the parent process (which did the syscall) receive a kill signal. > > Thanks > John > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message