From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 86995 invoked by alias); 12 Feb 2020 14:40:06 -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 85709 invoked by uid 89); 12 Feb 2020 14:40:06 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=HX-Languages-Length:966 X-HELO: conssluserg-05.nifty.com Received: from conssluserg-05.nifty.com (HELO conssluserg-05.nifty.com) (210.131.2.90) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 12 Feb 2020 14:40:03 +0000 Received: from Express5800-S70 (ntsitm196171.sitm.nt.ngn.ppp.infoweb.ne.jp [125.0.207.171]) (authenticated) by conssluserg-05.nifty.com with ESMTP id 01CEdnS0004604 for ; Wed, 12 Feb 2020 23:39:50 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com 01CEdnS0004604 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1581518390; bh=xG9kpwZlsBc+OqkLw3+TGk/NSR8PhSdAhofZ/PA7QdA=; h=Date:From:To:Subject:In-Reply-To:References:From; b=0WRqHvvBkQLsn/fG2TeJAAoUoqn22m3Sgz8F+kPUavlqEfE5ljc/drXlyQ/Ea7qb/ zOog/HMS6Q2ez3NBLiCz5Bs7c9Z6dYdeCEPHVvhPc12v+2gEpRyu30HdZWTy53C3l2 B6iK9Q2ujkWO3F2urJBegNlg1CqOcVVTOHh3YxobcFIEeDD3EafVqFG047KI6crmMN gLCsdQBmx2bDA7MJhkdX9BTYaQlHsuJaV3Q7CN9wk1a/S80ybTeCGR+zXp+JK+C6j8 Tvjp7LUvj6DWavIKccxZihKo1yJaxQE+Ntm8F0xDjaXfoRMJgKa1k0Wz1UClcRFZwY OhdqiIrE/JqGA== Date: Wed, 12 Feb 2020 14:40:00 -0000 From: Takashi Yano To: cygwin@cygwin.com Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages Message-Id: <20200212233958.ba07e020802e99de61eaf1b2@nifty.ne.jp> In-Reply-To: <2106ed38-d929-0663-8dd4-662252ebc7b4@cornell.edu> References: <6d43c714-c4ba-4f0c-9913-cb8453129c85@gmail.com> <93562f34-3a14-0c10-cb57-1ae861307d82@gmail.com> <810b0c97ee0697c06bdaa4dff4081bb502bc46ab.camel@dontech.dk> <9ed4b0776323e4a0f62191121715d52a0429bdb2.camel@dontech.dk> <23d3cd65794886745e2070a1d1b74013418b0bd8.camel@dontech.dk> <20200211112026.05664f5c68b6282a39da8ac2@nifty.ne.jp> <20200211221606.c82d718ec32a6d0ce3c2ad7b@nifty.ne.jp> <2106ed38-d929-0663-8dd4-662252ebc7b4@cornell.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00103.txt.bz2 On Tue, 11 Feb 2020 09:21:32 -0500 Ken Brown wrote: > On 2/11/2020 8:16 AM, Takashi Yano wrote: > > On Tue, 11 Feb 2020 11:38:35 +0100 > > Peter Dons Tychsen wrote: > >> On Tue, 2020-02-11 at 11:20 +0900, Takashi Yano wrote: > >>> Is this the same as your problem? > >> > >> Yeah, it could be. Could this result in fork error messages as we are > >> seeing all over the place? > > > > No. Fork error is not seen in my environment. This could be another > > problem. However, the code using kill() below is called also by fork(). > > So, it may be related. > > FWIW, I'm not seeing the fork error in my environment either. I see the hang > prior to your kill() patch, and then no problem (except for the ld error). I tested under Win10 1809 and found fork error occurs in that environment. Also confirmed the kill() patch fixes the issue. -- Takashi Yano -- 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