Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 22 Mar 2002 09:27:08 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Time sharing and fork Message-ID: <20020322142708.GE20338@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3C9B1A4D.32EE2167@axlog.fr> <3C9B287F.8E69BB6C@axlog.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/