Date: Thu, 12 May 2005 13:48:14 -0500 (CDT) From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= <sean-freebsd@farley.org> To: =?ISO-8859-1?Q?Herv=E9_Kergourlay?= <herve.kergourlay@atempo.com> Cc: hackers@freebsd.org Subject: Re: Porting on FreeBSD 53 Message-ID: <20050512134151.O2556@thor.farley.org> In-Reply-To: <428307A9.10901@atempo.com> References: <428307A9.10901@atempo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 12 May 2005, Hervé Kergourlay wrote: <snip> > 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 problems > to manage the fork and wait APIs ? > the second problem with calls is a blocking wait() call in the same condition > but this time the son process is finished but the wait call in the father > 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=77818) with zsh for my shell. You did suspend (sigsuspend()) SIGCHLD before the fork? By "fork fork", do you mean you fork twice? Seán -- sean-freebsd@farley.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050512134151.O2556>