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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=bLVEopcydm0PvVry
	gRqmZEXsqB3t1XAmm965vPPXTk/pgRJojx/4GaHNiSX9wZ42MbJJ2JJ3NRMJJOSl
	QFCTsaVErrrrLhoLyS4/pDY2BqA9inEBGciGBbhtYJu+RXaTrJCdSWLbo7scKBfP
	TVouudoR/RaKbubsrSEDBicl6Zk=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=06+hAM5xKWvUn6OeqGZV+8
	wrFM0=; b=U/Sj1UZJhjiomVv4XqRe5+rg5ZRJ9Y31NqHJs1xFb36ys2Y7WmgXnR
	O8sMEJDvPmArDsysiWP53E0sg7bIO9Qv+oFZRyizoVJSX4upq4RBdnoSJ4DoD7Z5
	HY6fZ9l5i5gajlCc5WYZcSOm/+GIdwig9lgN8zKA5/ZiPpwoC3yEY=
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=-1.3 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*r:sk:mailout, HX-HELO:sk:mailout, H*Ad:D*t-online.de, H*MI:sk:581AD3D
X-HELO: mailout07.t-online.de
Subject: Re: Windows 10 updates causes fork retry no child processes
To: cygwin AT cygwin DOT com
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>
From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker AT t-online DOT de>
Message-ID: <c7eebf5f-9f33-f5ae-70e7-da586f687725@t-online.de>
Date: Thu, 3 Nov 2016 15:31:01 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <581AD3D3.2020908@verizon.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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.

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