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=mCmx9H2qPAEk4ikuI34QrrH15d/b5S8KOuISMJcPGO0
	S00htc467cjNGEulyCxJIxF8/4zFzHJQg41s+nw1iTXaM2s2x0ALK+q12cyGKgus
	uhM7fDoRNQ+UceRq5mMnWmHCEXhB98ThgcecvXe9Ok9Ykc5wO63MkLOouEO2N6Zw
	=
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=eppQt+abfeHrbA8ZiTOpl+q97NQ=; b=QN34CVYbHQ8GdPOnq
	rxv7YwdiUsT+xilYkpvl7UiCNpR0tAxqCFCCVkTnHkEzD//IOUVv5NflkRIOlebw
	reShh51FliMykk61gOOtoAsTjREdrR1fex4kkMlqR6IRM5QzUay0G9TMmUxxwnNs
	3VoIV9NF+cKAEcdE1BGwsiDyic=
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.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=H*f:sk:3c30f95, H*RU:sk:omr-m01, Hx-spam-relays-external:sk:omr-m01, H*MI:sk:3c30f95
X-HELO: omr-m012e.mx.aol.com
Message-ID: <581B82D6.3020001@verizon.net>
Date: Thu, 03 Nov 2016 14:32:54 -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> <581B508D DOT 4050901 AT verizon DOT net> <3c30f952-23da-bdae-0743-d09320ac87da AT SystematicSw DOT ab DOT ca>
In-Reply-To: <3c30f952-23da-bdae-0743-d09320ac87da@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
x-aol-global-disposition: G
x-aol-sid: 3039ac1add8d581b82d72869
X-AOL-IP: 47.196.166.20
X-IsSubscribed: yes

On 11/03/2016 01:28 PM, Brian Inglis wrote:
> 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? I th
>

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?



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