X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org F08D43858C60 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca X-Authority-Analysis: v=2.4 cv=IaOU5Ema c=1 sm=1 tr=0 ts=61ea6490 a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17 a=IkcTkHD0fZMA:10 a=nThAchwBT9DRK9h6eSsA:9 a=QEXdDO2ut3YA:10 Message-ID: <59cdd990-5b36-7cc8-8d97-4f3c1f042535@SystematicSw.ab.ca> Date: Fri, 21 Jan 2022 00:45:19 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [EXTERNAL] Updated cygwin this morning, mintty window flashes briefly and quits Content-Language: en-CA To: cygwin AT cygwin DOT com References: From: Brian Inglis Organization: Systematic Software In-Reply-To: X-CMAE-Envelope: MS4xfHl1nm/i2fX2OjOW8zLapeH6INgpjboty9ZgctBtKU3t5jcNkFomHoFvaULyiXZXikji3ZnYdaBvloEFoLcyIKNbFa7HDnb4M9mL0LkHB/s2GmnG44v1 MexWXbMISYc/h9fwRuGGTQ7iPxQs6LuHk8cKQdBHhHlwKxf73+nYzfJi04ItS3MeiBQhQgRL3EmyYfnSmSZYnarv9HFurQsS+f8TRAbriOOfd0l8/tRDYL/m X-Spam-Status: No, score=-1160.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: cygwin AT cygwin DOT com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On 2022-01-20 13:24, Lavrentiev, Anton wrote: > There should be only one of them running, unless you have multiple Cygwin installations, > then there can be per-installation instances. Restart of all Cygwin processes was always > required (because the main DLL may not be properly replaced while it's in use by > any process) -- but a reboot usually took care of that quite well... > > Honestly, this was new for me, too. Formerly, install with a following reboot was all I needed > to do (since I'm not a power user on my work PC, that was the only way for me to "restart" > the service, anyways). But now the reboot alone does not seem to help anymore: looks like > Win10 loads up services in a different (fast) fashion, like a wake-up from hibernate. > So an explicit restart of cygserver is now required (and now I have to ask sysadmin > to do that for me at work -- sigh). I have modified my Cygwin services definitions to do Delayed Autostart and Preshutdown, with appropriate Windows service and inter-dependencies, shut them down and restart them in local scheduled tasks run under SYSTEM account on appropriate events and on demand, and restart them in a late local permanent postinstall script /etc/postinstall/zp_z0_l_start_services.dash after setup. Some combination of these techniques may allow your sysadmin to set things up for you to control these services without their intervention. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple