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:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=F1WnqTLnnueytoju
	XD0bFmnZkxUAf0ebuSdtG9J84jXnkIkNx5fGmfIG24/lA3tqfK5ILkMzFkddh/3X
	0t/iU1/kARWBUyOSx/9KqPgMCiTKoWrYaYHQx4ECPYEwozB9vNtojM41bScqzKHv
	Wg8EjwpzEQ6TWY7IjrpKBY8EU/0=
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:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=Rtr3L1qUu15eHNMu+JLhvX
	s3O2s=; b=mrCVLUtHBUh486VM0+YfqTIZ6yAUj81W/Cf4J0jtMh1FJ4tU+fmqUH
	TLTJaFmY54En/b1ZvU6+q7LvsVTaFXa1Nm9FTAMz1aaJDelrkIRavIkV3EvGkBRs
	f8ACOst5MBMjKFD89BTfQmAkhTkih/HwRWkschUcXMW+Au3kOxCaU=
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=0.4 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=Education, Alberta, etl, calgary
X-HELO:	smtp-out-so.shaw.ca
X-Authority-Analysis:	v=2.2 cv=abURpVgt c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=7C8xA_qTNELLStgM62sA:9 a=QEXdDO2ut3YA:10
Subject:	Re: Windows 10 updates causes fork retry no child processes
References:	<581A0AA5 DOT 5030107 AT verizon DOT net>
To:	cygwin AT cygwin DOT com
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID:	<0d98a082-e270-659f-5b48-b9dfd01fc85f@SystematicSw.ab.ca>
Date:	Wed, 2 Nov 2016 23:06:42 -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:	<581A0AA5.5030107@verizon.net>
X-CMAE-Envelope:	MS4wfMGii7VyGYRTWZgFvFdaWrq8HbcgvCdDtmP3jd691IBR18X4OqOtJHEteraRKYZ2hUI5RiHiv7/StwLsmdqaeft11NgGq/lM2P9a973YsEWTgomtiJ7x eCjl7XI9WLHZlwnO+5vmADeQaySL445x2KYcPAyDWlH5fCnURXC6Ts1PABAdpIlydw9CaTGPZcMZWQ==
X-IsSubscribed:	yes

On 2016-11-02 09:47, Gerry Reno wrote:
> Is there some automated way I can stop Windows 10 updates from
> continuously causing these fork retry no child process issues after
> every damn update?
> We use an application based on Cygwin (2.6.0) on our clients that
> gets wrecked everytime a Windows 10 update occurs.
> The users have no idea about Cygwin because it's hidden from them so
> I cannot ask them to do anything with regard to Cygwin.

> Any ideas for an automated way to stop these errors would be
> appreciated.

Could be caused by changed addresses used by Windows dlls, especially
if you are using the limited address space of Cygwin32.
After each update, have you tried shutting down all Cygwin processes
and either running setup unattended, if you sometimes do that, or a
full rebase from a cmd script?
For example:
c:\cygwin64\bin\dash /bin/rebase-trigger fullrebase
c:\cygwin64\bin\ash /bin/rebaseall

You can check if an update has been performed by caching and comparing
the timestamp and/or name of the last update log saved:

$ ls -lt --time-style=long-iso \
/proc/cygdrive/c/Windows/Logs/WindowsUpdate/WindowsUpdate.20??????.??????.???.?.etl \
| head -n 1

e.g.
-rwxr-x---+ 1 SYSTEM SYSTEM  77824 2016-11-02 22:27 /proc/cygdrive/c/Windows/Logs/WindowsUpdate/WindowsUpdate.20161102.214528.076.1.etl

and checking whether a restart has been been performed since to apply
the update by comparing against the output of:

$ date -d "now - `cut -d' ' -f1 /proc/uptime` seconds" +'%F %R'

e.g.
2016-10-22 19:44

in this case indicating Windows has not been (auto)restarted since
the update.

If you don't use mintty, you could do this in an ash or dash script
at Windows login, which does the rebase-trigger then exec rebaseall,
so no other process is running using Cygwin.

If you use Cygwin mintty you would have to do the equivalent from a
cmd or PowerShell script before launching any Cygwin process.

If your client systems run Windows Enterprise or Education or use
SCCM instead of Windows Update, details may need to be changed.

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