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=SfySFVwL0MQBOiRRBs9T3fe2IaVBmH/8tV/1kixQeUN
	vs5qvR42HJCknTZrOuF/Vsc29nDS9Pj/ZhqQ/YdqE6IpUOUegnjIYGHekVeYSDCH
	hDndNaBGNLv0ge9WYjwhq3/jul+pw978po9QeFxzK3yQiixDt5AYWF0f1pm7weio
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <581B508D.4050901@verizon.net>
Date: Thu, 03 Nov 2016 10:58:21 -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>
In-Reply-To: <c7eebf5f-9f33-f5ae-70e7-da586f687725@t-online.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 11/03/2016 10:31 AM, Hans-Bernhard Bröker wrote:
> Am 03.11.2016 um 07:06 schrieb Gerry Reno:
>
>> And the client machines are out in the field and not even connected to a network.
>
> If so, how/why do they ever hear about Windows updates in the first place?
>
>> What is needed is for Cygwin itself to detect and manage the situation.
>
> That is technically impossible.  The DLL rebasing procedure can only be done from _outside_ Cygwin.
>

They aren't connected permanently to an office network. 
They can connect to WiFi every so often when they get near to a WiFi location.

Ok, so why is automating this DLL rebasing procedure impossible?
I don't care if it is a Cygwin process or a Windows process that does this.
Something needs to check to see if the DLL rebasing needs done and then do it if that is the source of the problem.

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