public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Windows 10 updates causes fork retry no child processes
Date: Thu, 03 Nov 2016 17:28:00 -0000	[thread overview]
Message-ID: <3c30f952-23da-bdae-0743-d09320ac87da@SystematicSw.ab.ca> (raw)
In-Reply-To: <581B508D.4050901@verizon.net>

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?

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

  reply	other threads:[~2016-11-03 17:28 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
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 [this message]
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=3c30f952-23da-bdae-0743-d09320ac87da@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).