X-Recipient: archive-cygwin@delorie.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=bcfQPAydYbx6ZMA3N8UtJfH4LJm3dGy5D/jC0GyLccJ
	VLTp/YIkONjpGh3yr0q7CQLp36j/pkSKt0f05Mty8zakjN0ow2usK5kLrlu1WIrT
	1d3kM7QN6GtULoCiEYxljedGzCE8P6sLBa6J75eUwrDAtyLo0CC+hj7W7rX76M7c
	=
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=uRwXkmU2B+E1mi0XPLlr2kf2ctw=; b=SvrO/zuhpfBwd0qQl
	aiFXq5cS8rl3gvmg1AlFmr9K7zE4WnCdbBtbCElPFOyEmL6QTQUSGDawGG+clT8k
	OCk5OdcMIY4/s5nFCAR2V1e/kzKrqbCSWxcs3KX8HgQrL96XJekcL2VF5KpitFoa
	tPNriFBUpBvVOE2E5HhPKCdUk8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*f:sk:874m3nk, H*i:sk:874m3nk, H*MI:sk:874m3nk, Hx-languages-length:760
X-HELO: omr-m007e.mx.aol.com
Message-ID: <581D26E2.8030202@verizon.net>
Date: Fri, 04 Nov 2016 20:25:06 -0400
From: Gerry Reno <greno@verizon.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Windows 10 updates causes fork retry no child processes
References: <581A0AA5.5030107@verizon.net>	<0d98a082-e270-659f-5b48-b9dfd01fc85f@SystematicSw.ab.ca>	<581AD3D3.2020908@verizon.net>	<c7eebf5f-9f33-f5ae-70e7-da586f687725@t-online.de>	<581B508D.4050901@verizon.net>	<3c30f952-23da-bdae-0743-d09320ac87da@SystematicSw.ab.ca>	<581B82D6.3020001@verizon.net>	<86edbf6e-400a-f6fb-ddb8-d1134295b0c9@SystematicSw.ab.ca> <874m3nks1m.fsf@Rainer.invalid>
In-Reply-To: <874m3nks1m.fsf@Rainer.invalid>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
x-aol-sid: 3039ac1afe6d581d26e52f02
X-AOL-IP: 47.196.166.20
X-IsSubscribed: yes

On 11/04/2016 02:40 PM, Achim Gratz wrote:
> Brian Inglis writes:
>>> I think the simplest way for right now might be to have a batch file run at startup that runs rebaseall.
>>>
>>> Something like these lines in a batch file:
>>> cd C:\Cygwin\bin
>>> .\ash /bin/rebaseall
>>>
>>> This would rebase the dlls each time after Windows Update forces a reboot.
>>>
>>> Do you see any issue with that?
>> To set up for a full rebase you need to run the following first:
>>
>> .\dash /bin/rebase-trigger fullrebase
>>
>> otherwise it will run an incremental and probably do nothing.
> No, rebaseall is distinct from the incremental autorebase script.
>
>
> Regards,
> Achim.

Thanks for the clarification.


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

