From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4232 invoked by alias); 13 Feb 2020 04:14:27 -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 4221 invoked by uid 89); 13 Feb 2020 04:14:26 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy= X-HELO: conssluserg-04.nifty.com Received: from conssluserg-04.nifty.com (HELO conssluserg-04.nifty.com) (210.131.2.83) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 13 Feb 2020 04:14:24 +0000 Received: from Express5800-S70 (ntsitm196171.sitm.nt.ngn.ppp.infoweb.ne.jp [125.0.207.171]) (authenticated) by conssluserg-04.nifty.com with ESMTP id 01D4DLhl005373; Thu, 13 Feb 2020 13:13:22 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-04.nifty.com 01D4DLhl005373 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1581567202; bh=rjoqsLTTK5VYtNFjM5twJk1umSg31nt48RLAYfCSnM4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=oRraIXu8FyttFBUeFBK9j3b5TYXd/41+r34HFds6yuDCLPnirJlvG0K+yZ+eXdSzD dHPOlUGj4udyxqyn8uHg2G+2yhy9c0P3VH1hD6VAGdLw7Txd9pkO2JdzzDUfubqBYy dBoGAYgSo2YPCkYBeJTpX7SP0B0JqwTunajrCuIikSfT8Nk4M6BXvqkgvYPoCIMPY4 +SAJYVR51TvjbryRJ4B6iAO36g7XZR7wgt+MdQnYQ4TryTAzTud9foA0/AGzqWEmXR lLyk9A577ICWGKXXp8izfpOR3OAhWj/+oH4kVvWyyVCESABqgGgNtPqcOirCe2XCPa JxLjbgYwrkb2Q== Date: Thu, 13 Feb 2020 04:14:00 -0000 From: Takashi Yano To: pdt@dontech.dk Cc: cygwin@cygwin.com Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages Message-Id: <20200213131322.66b104901134c644c0dad57e@nifty.ne.jp> In-Reply-To: <3971cde6277a16cb04ac25067b4478b9cfbfa319.camel@dontech.dk> 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> <03033cd520c633f90e503414f1b678b4a9283d33.camel@dontech.dk> <20200212112411.32f05ee5ce2c1401bd076746@nifty.ne.jp> <3971cde6277a16cb04ac25067b4478b9cfbfa319.camel@dontech.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00108.txt.bz2 On Wed, 12 Feb 2020 11:54:02 +0100 Peter Dons Tychsen wrote: > Hi Takashi, > > On Wed, 2020-02-12 at 11:24 +0900, Takashi Yano wrote: > > My failure in pty code was that I used kill() in pty system > > calls. kill() can be used check if the process is still alive > > by passing signal number of 0 to the second argument. It returns > > -1 if the process already exited. However, in this case errno > > is set to ESRCH. As a result, the errno value which pty system > > call set is accidentally overwritten by kill(). > > OK, thanks for clearing all that up. Just wanted to make sure kill() > was not buggy :-). > > I will test the committed patch and the upcoming release vigerously to > see if there are still bugs to be found in this area. Not sure why i > get fork() errors and you do not (my tests with the example i made > always causes fork() errors in 3.1.2). > > Thanks for all the help and your snappy replies, Could you please try latest snapshot? https://cygwin.com/snapshots/ -- 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