X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0	tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Message-ID: <32040454.post@talk.nabble.com>
Date: Mon, 11 Jul 2011 12:14:22 -0700 (PDT)
From: Marc Girod <marc DOT girod AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Random fork failures
In-Reply-To: <20110711173425.GA5484@ednor.casa.cgf.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <4E1AAF38 DOT 9040100 AT gmail DOT com> <20110711082740 DOT GC8249 AT calimero DOT vinschen DOT de> <4E1AB60C DOT 7050902 AT gmail DOT com> <20110711090218 DOT GA22947 AT calimero DOT vinschen DOT de> <4E1AC212 DOT 7030806 AT gmail DOT com> <20110711095630 DOT GB22947 AT calimero DOT vinschen DOT de> <4E1ACF65 DOT 6070102 AT gmail DOT com> <20110711114747 DOT GD22947 AT calimero DOT vinschen DOT de> <20110711120430 DOT GE22947 AT calimero DOT vinschen DOT de> <4E1AFE3A DOT 4070406 AT gmail DOT com> <CAGHJv4dMnBfpM5jr_O8urBrpdbTD2+D2U1LVgwGJsEs471thyg AT mail DOT gmail DOT com> <20110711173425 DOT GA5484 AT ednor DOT casa DOT cgf DOT cx>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com



Christopher Faylor-8 wrote:
> 
> Actually, I think it is more likely BLODA.
> 
The other standard reply (I am surprised not to read it in this thread) is
rebaseall.

I boot my laptop about weekly.
That's the moment I use to refresh cygwin, especially if there has been some
forced upgrades
(frequent in our environment).
At that point, I'll experiment fork multiple errors, at X and emacs startup.
To this, I reply by running in ash .rebaseall && ./peflagsall, until I get a
clean start.
On top of this, I do a perlrebase, and usually, I am covered.
I understand that every rebase will raise the base address where to load
injected DLLs.

Is this just fantasy and rain dancing?
[ A fork error with scp may get my system to hang so that I need to reboot ]
Marc
-- 
View this message in context: http://old.nabble.com/Random-fork-failures-tp32035530p32040454.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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