From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 01:22:40 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D2AC16A41F; Tue, 24 Jan 2006 01:22:40 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id C95C943D48; Tue, 24 Jan 2006 01:22:38 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail27.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0O1MacB030022 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Jan 2006 12:22:37 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k0O1MaHh037679; Tue, 24 Jan 2006 12:22:36 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k0O1Ma49037678; Tue, 24 Jan 2006 12:22:36 +1100 (EST) (envelope-from pjeremy) Date: Tue, 24 Jan 2006 12:22:36 +1100 From: Peter Jeremy To: Daniel Eischen Message-ID: <20060124012236.GU25397@cirb503493.alcatel.com.au> References: <43D56E79.60504@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 01:22:40 -0000 On Mon, 2006-Jan-23 19:59:02 -0500, Daniel Eischen wrote: >POSIX specifies that only 1 thread (the forking thread) is present >after a fork. Just to clarify, I presume you are talking about only one thread existing in the child process and the parent's threads still exist as they did before the fork(). If fork() arbitrarily killed all the threads in the parent process, that would be a real PITA. -- Peter Jeremy