From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36661 invoked by alias); 11 Feb 2020 21:31:25 -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 36577 invoked by uid 89); 11 Feb 2020 21:31:24 -0000 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 Received: from leela03.telenor.dk (HELO leela03.telenor.dk) (212.88.64.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Feb 2020 21:31:17 +0000 X-MtScore: NO score=0 Received: from donpedro.P-2601HN-F1 (unknown [94.147.60.8]) by leela03.telenor.dk (Telenor Denmark) with ESMTP id 93312C13689B; Tue, 11 Feb 2020 22:31:13 +0100 (CET) Message-ID: <03033cd520c633f90e503414f1b678b4a9283d33.camel@dontech.dk> Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages From: Peter Dons Tychsen Reply-To: pdt@dontech.dk To: Takashi Yano , cygwin@cygwin.com Date: Tue, 11 Feb 2020 21:31:00 -0000 In-Reply-To: <20200211221606.c82d718ec32a6d0ce3c2ad7b@nifty.ne.jp> 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> 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 X-SW-Source: 2020-02/txt/msg00100.txt.bz2 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