From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 46586 invoked by alias); 3 Nov 2016 14:31:34 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 46569 invoked by uid 89); 3 Nov 2016 14:31:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*r:sk:mailout, HX-HELO:sk:mailout, H*Ad:D*t-online.de, H*MI:sk:581AD3D X-HELO: mailout07.t-online.de Received: from mailout07.t-online.de (HELO mailout07.t-online.de) (194.25.134.83) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 03 Nov 2016 14:31:32 +0000 Received: from fwd30.aul.t-online.de (fwd30.aul.t-online.de [172.20.26.135]) by mailout07.t-online.de (Postfix) with SMTP id D5D5C424626B for ; Thu, 3 Nov 2016 15:31:29 +0100 (CET) Received: from [192.168.2.28] (bKEY8TZvohuSi45FVs-8ij+TWUgI7kko4G+RmMYL94CUjjJd7tJSTSZx1MKJGXCZV7@[91.59.24.114]) by fwd30.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1c2J35-0Ks49o0; Thu, 3 Nov 2016 15:31:23 +0100 Subject: Re: Windows 10 updates causes fork retry no child processes To: cygwin@cygwin.com References: <581A0AA5.5030107@verizon.net> <0d98a082-e270-659f-5b48-b9dfd01fc85f@SystematicSw.ab.ca> <581AD3D3.2020908@verizon.net> From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= Message-ID: Date: Thu, 03 Nov 2016 14:31:00 -0000 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: <581AD3D3.2020908@verizon.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-11/txt/msg00024.txt.bz2 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. -- 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