X-Recipient: archive-cygwin@delorie.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:message-id:subject:from:reply-to:to:date
	:in-reply-to:references:content-type:mime-version
	:content-transfer-encoding; q=dns; s=default; b=cOw2/QBbwRXv6btI
	RV83g1prOY/R3Odq+scgePBnLquwwIBRNKwyUot8upH9/6+2KndKGwS0S1QCbuVb
	BW/Pk5/SayzMFdl9TOp21rh1/2jxhpYsIODQV4A8LQrI5y1/NTP+9kbALyumXAbn
	Ta1UtKwUa1+BLmxthL7Osfm6Aew=
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:message-id:subject:from:reply-to:to:date
	:in-reply-to:references:content-type:mime-version
	:content-transfer-encoding; s=default; bh=QeEgeo+YKW2DLt4sk4x2cY
	hMK0Y=; b=ZOJom8gA8h3uJIXVTrhmAVk7qidn9bbbXM2xVPNyafn7fgDDBqx73E
	bNxP5EOux52dmrBvue7R1+PW0MwEwgT6+FBa+y2iFKu8fkxEfkeKkRQVlK3lwtFs
	Fna3iaUuoa1npvp7LwqcD/qpLoOvLklr1neHyS4yLszMpKGmaRtW0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 spammy=
X-HELO: leela03.telenor.dk
X-MtScore: NO score=0
Message-ID: <03033cd520c633f90e503414f1b678b4a9283d33.camel@dontech.dk>
Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages
From: Peter Dons Tychsen <pdt@dontech.dk>
Reply-To: pdt@dontech.dk
To: Takashi Yano <takashi.yano@nifty.ne.jp>, cygwin@cygwin.com
Date: Tue, 11 Feb 2020 22:31:12 +0100
In-Reply-To: <20200211221606.c82d718ec32a6d0ce3c2ad7b@nifty.ne.jp>
References: <6d43c714-c4ba-4f0c-9913-cb8453129c85@gmail.com>	 <d24aa066-ab3d-9ff0-215a-0a1ed1ec2e5d@cornell.edu>	 <93562f34-3a14-0c10-cb57-1ae861307d82@gmail.com>	 <f4a808cf-d129-f6ce-0da8-674cf88a71ad@gmail.com>	 <810b0c97ee0697c06bdaa4dff4081bb502bc46ab.camel@dontech.dk>	 <CACSsrOzmexPqVeAoZigrkR4Tv6sWa-506Ui8UzsgLcTSBotgLw@mail.gmail.com>	 <9ed4b0776323e4a0f62191121715d52a0429bdb2.camel@dontech.dk>	 <d5109f77-9d73-fd68-fac6-1119037c8468@gmail.com>	 <23d3cd65794886745e2070a1d1b74013418b0bd8.camel@dontech.dk>	 <20200211112026.05664f5c68b6282a39da8ac2@nifty.ne.jp>	 <b3f992f6b2ba69b9f29e2b126e8580e76d98e4a8.camel@dontech.dk>	 <20200211221606.c82d718ec32a6d0ce3c2ad7b@nifty.ne.jp>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.5 (3.32.5-1.fc30)
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

Hi Takashi,

Thanks for your effort.

On Tue, 2020-02-11 at 22:16 +0900, Takashi Yano wrote:
> however, I found the real cause is that errno is accidentally set
> by kill() in pty system calls. That is, the problem is not in the
> kill() itself but in usage of it. Cygwin older than 3.1.0 does not
> have these code in pty. 

OK, is there a fix for that or is that the fix you already pushed? And
what is wrong with the usage of kill(). How can kill() be used
incorrectly?

Is there are more things here it would be great to get them in for the
3.1.3 release.

Thanks,

/pedro


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

