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=SfySFVwL0MQBOiRRBs9T3fe2IaVBmH/8tV/1kixQeUN
	vs5qvR42HJCknTZrOuF/Vsc29nDS9Pj/ZhqQ/YdqE6IpUOUegnjIYGHekVeYSDCH
	hDndNaBGNLv0ge9WYjwhq3/jul+pw978po9QeFxzK3yQiixDt5AYWF0f1pm7weio
	=
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=dNJ0BGeE+AiI/sIURgrD1dA59iw=; b=xDOy/rzrATVSriRZk
	3wzQP8kXdwK86DYRuVsycdKsnGdodfxOvIG1oFvzLIRRJsyyxwZzz0J/YMsIOvVQ
	dIg7M0WY7uiYECA3ILWkEzvz5uIrD9dLXX0XAjfiU25VI4IfNzLW+5LlcKAAN8yX
	27a2gYYa9e/2uUmU4fNpwnMGDo=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=wifi, WiFi, H*MI:sk:c7eebf5, Hx-spam-relays-external:sk:omr-m00
X-HELO: omr-m009e.mx.aol.com
Message-ID: <581B508D.4050901@verizon.net>
Date: Thu, 03 Nov 2016 10:58:21 -0400
From: Gerry Reno <greno AT verizon DOT 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 AT cygwin DOT com
Subject: Re: Windows 10 updates causes fork retry no child processes
References: <581A0AA5 DOT 5030107 AT verizon DOT net> <0d98a082-e270-659f-5b48-b9dfd01fc85f AT SystematicSw DOT ab DOT ca> <581AD3D3 DOT 2020908 AT verizon DOT net> <c7eebf5f-9f33-f5ae-70e7-da586f687725 AT t-online DOT de>
In-Reply-To: <c7eebf5f-9f33-f5ae-70e7-da586f687725@t-online.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
x-aol-global-disposition: G
x-aol-sid: 3039ac1adfcd581b508d54a6
X-AOL-IP: 47.196.166.20
X-IsSubscribed: yes

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