This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Time sharing and fork

From: Christopher Faylor <cygwin at cygwin dot com>
To: cygwin at cygwin dot com
Date: Fri, 22 Mar 2002 09:27:08 -0500
Subject: Re: Time sharing and fork
References: <FC169E059D1A0442A04C40F86D9BA76008AB5B@itdomain003.itdomain.net.au> <3C9B1A4D.32EE2167@axlog.fr> <3C9B287F.8E69BB6C@axlog.fr>
Reply-to: cygwin at cygwin dot com

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/

Follow-Ups:
- Re: Time sharing and fork
  - From: Stephane Corbe

References:
- RE: alarm();pause();alarm();pause(); doesn't pause in pthread
  - From: Robert Collins
- Time sharing and fork
  - From: Stephane Corbe
- Re: Time sharing and fork
  - From: Stephane Corbe

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]