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:from:to:subject:references:date:in-reply-to :message-id:mime-version:content-type; q=dns; s=default; b=dqwRr DuHTXfPV0VY9VfH1qd4FXtnIKGurbf/GJCgZhNCospV5GGNywCVPgBgszSomS7ww KEnn3ly46P5T32/+t468cI9u4lBRujp73GkhzOS/luBAKHHsceaTUrPZW8qw+wSX WDnPHo4Gs+oAdPs+UgTAZ74P+6OWR/tLKQ9FAU= 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:from:to:subject:references:date:in-reply-to :message-id:mime-version:content-type; s=default; bh=mOvdmNmIZw/ lXbri6nP4DrsKgU0=; b=fLkb6QvPlT5p9xtG4tiksnTeffDxGWwPaSvnNL4i/X7 mUtYaCHnYnQTBt+DolwmhOJHCY2N4bhyWLcTq/SPkBxpXxAVILhasWqI7CDCazfu CVf4EJN1N5O1IkSI1He18Y5JHXfQ4VyVBlMov4SqJ8EH7TTsxnCCBP87/9wbKz7U = 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=-1.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-in-16.arcor-online.net X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-11.arcor-online.net 3lxxJg6vjVzVTh9 From: Achim Gratz To: cygwin AT cygwin DOT com Subject: Re: Cygwin fork:retry error References: <55663419 DOT 6080700 AT verizon DOT net> Date: Thu, 28 May 2015 06:44:31 +0200 In-Reply-To: <55663419.6080700@verizon.net> (Gerry Reno's message of "Wed, 27 May 2015 17:16:09 -0400") Message-ID: <87h9qxwbtc.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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