Windows 10 updates causes fork retry no child processes
Thu Nov 3 13:42:00 GMT 2016
On 11/03/2016 09:00 AM, Brian Inglis wrote:
> On 2016-11-03 00:06, Gerry Reno wrote:
>> On 11/03/2016 01:06 AM, Brian Inglis wrote:
>>> 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
>>> 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
>>> -rwxr-x---+ 1 SYSTEM SYSTEM 77824 2016-11-02 22:27
>>> 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'
>>> 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.
>> The users cannot do anything with Cygwin.
>> And the client machines are out in the field and not even connected
>> to a network.
>> What is needed is for Cygwin itself to detect and manage the
> Myself and others are not seeing these specific problems every update.
> You may want to try following the problem reporting guidelines for help.
> You need to see if you can diagnose and fix these problems in the
> clients' environment by getting access and trying disabling or
> deinstalling BLODAs or running rebaseall.
> If you can do that, you can try patching setup, or writing scripts,
> to provide a fix.
> Finally, you can try submitting those patches upstream to Cygwin for
> inclusion in setup, or as a separate package performing the fix.
We are only seeing this on the newer W10 machines.
W8 machines don't exhibit this problem.
And both have the exact same set of software installed on them.
So there must be something different about W10.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin