Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 22 Mar 2002 09:27:08 -0500
From: Christopher Faylor <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Time sharing and fork
Message-ID: <20020322142708.GE20338@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <FC169E059D1A0442A04C40F86D9BA76008AB5B AT itdomain003 DOT itdomain DOT net DOT au> <3C9B1A4D DOT 32EE2167 AT axlog DOT fr> <3C9B287F DOT 8E69BB6C AT axlog DOT fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3C9B287F.8E69BB6C@axlog.fr>
User-Agent: Mutt/1.3.23.1i

On Fri, Mar 22, 2002 at 12:50:07PM +0000, Stephane Corbe wrote:
>An interresting part of strace traces of the programm show well that the
>child didn't start before the death of his father :

That's not guaranteed fork behavior.  If the child never started, that would
be a bug.  There is no guaranteed behavior with respect to which process is
scheduled after a fork on windows or linux.  If you want to serialize things
use one of the wait calls.

cgf
--
Please do not send me personal email with cygwin questions.
Use the resources at http://cygwin.com/ .

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/