X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=lyN+hUt9e1gLLdB0Gi5u4GR1AIYOdjIIzXVY4N5llwi
	BpzGIsi9RJhvBWJQaSMbGXCcbl5Zm9zHOhm0vf5Toe/e0RxOMSJt2MKdzqfj7z1d
	1riZWWQcdZfV69LzOi6vq5an1U0F4aFzvetdvQZH+V/lDbDmBr1RrSHswDQHypVc
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=UPPKjtFx/weDviNpuPT/DjGaawA=; b=P7dK8aH/MgSP78eot
	ijnGhB9GIFBJfBm2SZ1j85pITLZC9b+g7LyBxX2LP7RkIVgdF08qYzYgydZXtD/D
	eywuxzRwk5pKAONR6KzODfsdLic8HC6IebqtyYr6VBQr+Isy2zD94yxCKd+AXCsV
	N9Bt2YvyE9kE+4P7ibkpnyfooU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
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
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 23:39:58 +0900
From: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
To: cygwin AT cygwin DOT 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 AT gmail DOT com>	<d24aa066-ab3d-9ff0-215a-0a1ed1ec2e5d AT cornell DOT edu>	<93562f34-3a14-0c10-cb57-1ae861307d82 AT gmail DOT com>	<f4a808cf-d129-f6ce-0da8-674cf88a71ad AT gmail DOT com>	<810b0c97ee0697c06bdaa4dff4081bb502bc46ab DOT camel AT dontech DOT dk>	<CACSsrOzmexPqVeAoZigrkR4Tv6sWa-506Ui8UzsgLcTSBotgLw AT mail DOT gmail DOT com>	<9ed4b0776323e4a0f62191121715d52a0429bdb2 DOT camel AT dontech DOT dk>	<d5109f77-9d73-fd68-fac6-1119037c8468 AT gmail DOT com>	<23d3cd65794886745e2070a1d1b74013418b0bd8 DOT camel AT dontech DOT dk>	<20200211112026 DOT 05664f5c68b6282a39da8ac2 AT nifty DOT ne DOT jp>	<b3f992f6b2ba69b9f29e2b126e8580e76d98e4a8 DOT camel AT dontech DOT dk>	<20200211221606 DOT c82d718ec32a6d0ce3c2ad7b AT nifty DOT ne DOT jp>	<2106ed38-d929-0663-8dd4-662252ebc7b4 AT cornell DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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 <takashi DOT yano AT nifty DOT ne DOT jp>

--
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