From: Evgeny Grin <k2k@yandex.ru>
To: cygwin@cygwin.com
Subject: Re: Windows 10 updates causes fork retry no child processes
Date: Wed, 02 Nov 2016 17:31:00 -0000 [thread overview]
Message-ID: <f8327d4c-37cd-9afb-824c-1a5ce96bfc89@yandex.ru> (raw)
In-Reply-To: <581A0AA5.5030107@verizon.net>
On 02.11.2016 18: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.
Seems that you have two options:
* Ask Microsoft to stop breaking Windows in Preview builds (according to
my personal research - Windows unloads wrong .DLL instead of requested .DLL)
* Ask your clients not to use Insider Preview because of "beta nature"
of those builds.
--
Best Wishes,
Evgeny Grin
--
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
next prev parent reply other threads:[~2016-11-02 17:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 15:47 Gerry Reno
2016-11-02 17:31 ` Evgeny Grin [this message]
2016-11-03 0:05 ` Gerry Reno
2016-11-03 5:06 ` Brian Inglis
2016-11-03 6:06 ` Gerry Reno
2016-11-03 7:02 ` Marco Atzeri
2016-11-03 13:01 ` Brian Inglis
2016-11-03 13:42 ` Gerry Reno
2016-11-03 13:46 ` Eliot Moss
2016-11-03 17:08 ` Brian Inglis
2016-11-03 14:31 ` Hans-Bernhard Bröker
2016-11-03 14:58 ` Gerry Reno
2016-11-03 17:28 ` Brian Inglis
2016-11-03 18:33 ` Gerry Reno
2016-11-03 18:47 ` Achim Gratz
2016-11-03 19:02 ` Gerry Reno
2016-11-03 19:11 ` Achim Gratz
2016-11-03 22:08 ` Brian Inglis
2016-11-03 22:28 ` Gerry Reno
2016-11-04 18:40 ` Achim Gratz
2016-11-05 0:25 ` Gerry Reno
2016-11-07 16:17 ` L. A. Walsh
2016-11-03 9:13 ` Marko Božiković
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f8327d4c-37cd-9afb-824c-1a5ce96bfc89@yandex.ru \
--to=k2k@yandex.ru \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).