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:references:to:from:reply-to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=NjmJkzvQxQvymO4b
	okkCFOhkEXNpwkBq4auW9QWdSbrXzzI3XZwuEpZ+WxUsz2yWSMz1gP/Nvry5Meo+
	COSy2DaGVb92IVh610JzdHHdcrt4XdRsOyVLnd3GkAkCXHnA1mruUMMb7WUq4Bub
	fPC/wv1z9Po6YE8WTS55H3rVWNY=
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:references:to:from:reply-to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=8SkDqfCO5O841wV2xWXOAW
	KqKiQ=; b=auLcZudk0ovtNsME3V0Ttpk+6zObOTY2xYlRDssUQDvPbqvYReqhPn
	KEePpm0sW8WdhWTtJfc3MCZULAIlntD+MuC71frE4BCC6PmbHisY7eM3OpKM2ktb
	D4R8sTIrFBKeamygPEp+QTqB3LM8USkYSvzJJ6k5jFdvUJ+U2oR5o=
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.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*r:ip*192.168.1.100, H*RU:64.59.136.137, Hx-spam-relays-external:!192.168.1.100!, Hx-spam-relays-external:64.59.136.137
X-HELO:	smtp-out-so.shaw.ca
X-Authority-Analysis:	v=2.2 cv=SPoybKnH c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=dIDegm6Mw7e5aFJXRNIA:9 a=QEXdDO2ut3YA:10
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> <581B508D DOT 4050901 AT verizon DOT net>
To:	cygwin AT cygwin DOT com
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Message-ID:	<3c30f952-23da-bdae-0743-d09320ac87da@SystematicSw.ab.ca>
Date:	Thu, 3 Nov 2016 11:28:17 -0600
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:	<581B508D.4050901@verizon.net>
X-CMAE-Envelope:	MS4wfATcho4mg6fO0CqqiakQsQD9geDnQRcdwZttqf2hoq9AmAzH/9GHUmp+1W0xESCd0CM9Yu7cIKoiHhMYR47inoBU/Kgq0zNBueHILJvUFqKLdKA8FJHd wOHXArt0UBjrPEbwaAGgtWGJuDHXSpIUG48x6hnVkROLqy9pUu+3TbxcuTr086bP0zj5T+pRc1Ds2A==
X-IsSubscribed:	yes

On 2016-11-03 08:58, Gerry Reno wrote:
> 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.

Maybe your clients' problem is that W10 is now dynamically loading wifi
or network dlls into the stack and being a total BLODA?
Your app setup, your clients, so *you* need to do the data collection
and diagnosis, ask for help here, test fixes.
At least a cygcheck -rsv from a problem system, attached to a post,
would let the dogs here see the shape of the bone to help you.

As with other off-net systems, there should be some auto-reporting
system built in where you can capture and send problem logs.
Maybe you could change the env setting for:
CYGWIN=error_start=C:/cygwin64/bin/dumper
(use slashes instead of doubled backslashes)
to run cygcheck -hrsv > cygcheck.txt instead, perhaps from a cmd
script, and queue it for mailing to you when connected?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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

- Raw text -