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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=qC3hss3P4qnMjv4YijUlzBGM/8pYpJDLcItiZcOqpdM LAeRfBkBfW181ZbWtD868W3vSUv6TUOj/YS8Yk4NfN77mZ/cqDUb7OynKwrwnyV2 Obu7X+zBEvs8dWJYBTaCLX+d5iqDCcedEiDVlzPYN6yLzCVsw8ky9yrMx9Wisbt8 = 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:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=yiZLHBLIF9cR8B5cbZVinQzNOt8=; b=itI2kEpDvylzRo6z/ sKKYXSRPGbmxhx6bTIWktdHkYRmSqXwifsPuKhTd+MQa/K/fMZl0Yte7VdBl2XrE xIE+7omEMgWebA6IynLjGgTpA9Bw7q99IbqiOZxBfnGtf6JolKOgEMHcuFGxBM9s dpdbwy95dO40VUgIteA9Ec786M= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_50,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: tmta134047pub.verizon.net X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=QoejpgGd c=1 sm=1 tr=0 a=ezFLAP4FW/eYWxKiKgkjNA==:117 a=9-f_Eo4EFxIA:10 a=IkcTkHD0fZMA:10 a=o1OHuDzbAAAA:8 a=oR5dmqMzAAAA:8 a=XAFQembCKUMA:10 a=pxJTKy-PTJwirem-7MUA:9 a=faBIIyLy5Hj1b8up:21 a=e2YoK9s6oI9HD2la:21 a=QEXdDO2ut3YA:10 Message-id: <55759578.8070903@verizon.net> Date: Mon, 08 Jun 2015 09:15:36 -0400 From: Gerry Reno User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin fork:retry error References: <55663419 DOT 6080700 AT verizon DOT net> <87h9qxwbtc DOT fsf AT Rainer DOT invalid> In-reply-to: <87h9qxwbtc.fsf@Rainer.invalid> Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 7bit X-IsSubscribed: yes On 05/28/2015 12:44 AM, Achim Gratz wrote: > Gerry Reno writes: >> I've been struggling with this fork:retry issue for over a month and have yet to find a working solution. >> >> The machines are Windows 7 64-bit with Cygwin 32-bit installation. >> I run Setup and then install some bash scripts for the user. >> Only some of the machines appear to be having this fork:retry problem. >> And even reinstalling Cygwin does not appear to fix the problem. > That's the hallmark of BLODA. > >> Error: >> >> /etc/profile: fork: retry: Resource temporarily unavailable >> 1 [main] bash 3236 child_info_fork::abort: C:\Cygwin\bin\cyggcc_s-1.dll: loaded to different address: >> parent(0x370000) != child(0x2B0000) > These very low addresses again point to BLODA. > >> I've tried completely eliminating every trace of Cygwin I can find on the machine and then reinstalling Cygwin but the >> error persists. > It's very likely not caused by Cygwin, so this route isn't even starting > to address the issue. > >> I've tried the rebaseall commands listed in a number of posts. Again, the error persists. > BLODA. > >> What's interesting is that if I try rebooting one of these machines numerous times eventually the scripts will work >> without this fork:retry error. > BLODA. > >> But if you reboot the machine again most likely the fork:retry error will reappear. >> It's almost like there is some race condition involved. > BLODA. > >> Any help here greatly appreciated. > Check if you have any real-time virus scanner activated and except the > Cygwin installation tree from being acted on if possible. And since > it's not likely you can just deactivate the virus scanner for production > machines, at the very least you need to ensure that you don't have _two_ > of them active on the machine (this would produce extremely "funny" > behaviour) and the one that is active is configured the same on all of > them. > > > Regards, > Achim. The only way that we found to fix this fork:retry problem 100% was to uninstall BitDefender Endpoint Security entirely on each client and reinstall it after we installed Cygwin. BitDefender does not currently give you any way to disable its Endpoint Security client. As you can imagine this was quite an impact. Gerry -- 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