From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Windows 10 updates causes fork retry no child processes
Date: Thu, 03 Nov 2016 07:02:00 -0000 [thread overview]
Message-ID: <a13ffcd0-7a68-860b-65f0-65a9f918b97f@gmail.com> (raw)
In-Reply-To: <581AD3D3.2020908@verizon.net>
On 03/11/2016 07:06, Gerry Reno wrote:
>> 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 situation.
>
than it was chosen the wrong system.
Instead of W10 + Cygwin a Linux system was more indicated.
Cygwin can not avoid that other programs, poorly written,
interfere with it.
https://cygwin.com/faq/faq.html#faq.using.bloda
You need to get rid of them.
Regards
Marco
--
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-03 7:02 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
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 [this message]
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=a13ffcd0-7a68-860b-65f0-65a9f918b97f@gmail.com \
--to=marco.atzeri@gmail.com \
--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).