From owner-freebsd-hackers@FreeBSD.ORG Thu May 12 18:48:29 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27D6716A4CE for ; Thu, 12 May 2005 18:48:29 +0000 (GMT) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id A34BB43D76 for ; Thu, 12 May 2005 18:48:28 +0000 (GMT) (envelope-from sean-freebsd@farley.org) Received: from thor.farley.org (thor.farley.org [IPv6:2001:470:1f01:290:1::5]) by mail.farley.org (8.13.1/8.13.1) with ESMTP id j4CImHRn047470; Thu, 12 May 2005 13:48:17 -0500 (CDT) (envelope-from sean-freebsd@farley.org) Received: from localhost (localhost [127.0.0.1]) by thor.farley.org (8.13.3/8.13.3) with ESMTP id j4CImEot002612; Thu, 12 May 2005 13:48:15 -0500 (CDT) (envelope-from sean-freebsd@farley.org) Date: Thu, 12 May 2005 13:48:14 -0500 (CDT) From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= To: =?ISO-8859-1?Q?Herv=E9_Kergourlay?= In-Reply-To: <428307A9.10901@atempo.com> Message-ID: <20050512134151.O2556@thor.farley.org> References: <428307A9.10901@atempo.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1023258206-1115923694=:2556" cc: hackers@freebsd.org Subject: Re: Porting on FreeBSD 53 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2005 18:48:29 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1023258206-1115923694=:2556 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 12 May 2005, Herv=E9 Kergourlay wrote: > 4) wait() API > > 2 problems, the first is a ECHILD error on a wait call after a fork fork > The code is generic for most of unix system. Is there any specific proble= ms=20 > to manage the fork and wait APIs ? > the second problem with calls is a blocking wait() call in the same condi= tion=20 > but this time the son process is finished but the wait call in the father= =20 > stays blocked, again it's a generic Unix code > > If there is no evidence, ask me for more informations The second problem sounds like what I am encountering (http://www.freebsd.org/cgi/query-pr.cgi?pr=3D77818) with zsh for my shell. You did suspend (sigsuspend()) SIGCHLD before the fork? By "fork fork", do you mean you fork twice? Se=E1n --=20 sean-freebsd@farley.org --0-1023258206-1115923694=:2556--