From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30185 invoked by alias); 27 Jun 2013 21:58:05 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 30153 invoked by uid 89); 27 Jun 2013 21:58:01 -0000 X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 Received: from mail-pa0-f49.google.com (HELO mail-pa0-f49.google.com) (209.85.220.49) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 27 Jun 2013 21:58:00 +0000 Received: by mail-pa0-f49.google.com with SMTP id ld11so1587230pab.36 for ; Thu, 27 Jun 2013 14:57:59 -0700 (PDT) X-Received: by 10.67.3.99 with SMTP id bv3mr8186853pad.140.1372370279153; Thu, 27 Jun 2013 14:57:59 -0700 (PDT) Received: from [192.168.0.101] (S0106000cf16f58b1.wp.shawcable.net. [24.79.212.134]) by mx.google.com with ESMTPSA id fm2sm5517516pab.13.2013.06.27.14.57.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 14:57:57 -0700 (PDT) Message-ID: <51CCB56A.8010705@users.sourceforge.net> Date: Thu, 27 Jun 2013 21:59:00 -0000 From: "Yaakov (Cygwin/X)" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Failure with fork() References: <51CC8EE9.1080401@gmail.com> <51CCA6FB.5060804@users.sourceforge.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2013-06/txt/msg00709.txt.bz2 http://cygwin.com/acronyms/#PPIOSPE ! On 2013-06-27 16:52, Alan W. Irwin wrote: > Once the relevant snapshot is released I will let you know how far I The 20130627 snapshot is now available. > get with a variant of the above I have thought of which is replacing > cygwin1.dll on the fly when the individual step of the initial run of > setup.exe that installs cygwin1.dll is completed. That method takes > advantage of the fact that the fork issue only occurs during the final > step of the install and presumably nothing is using cygwin1.dll when > the prior step that installs cygwin1.dll is completed. So ideally > this method would be completely error free, but I will see about that, > and if not I will fall back to trying your method. That might just work, if you get the timing right. Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple