From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) by sourceware.org (Postfix) with ESMTPS id 1DC00393BC0B for ; Tue, 3 Aug 2021 18:20:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1DC00393BC0B X-UI-Sender-Class: 214d933f-fd2f-45c7-a636-f5d79ae31a79 Received: from johndoe65534.mail.com ([85.28.102.11]) by smtp.mail.com (mrgmxus005 [74.208.5.15]) with ESMTPSA (Nemesis) id 0LcAex-1mthtn0pSH-00je1o for ; Tue, 03 Aug 2021 20:20:34 +0200 Subject: Re: Unable to start Cygwin64 terminal after password change To: cygwin@cygwin.com References: <771e99c7-19c5-df67-abf2-fefde0e4d7b5@SystematicSw.ab.ca> <57515f66-8c88-5078-8726-4883f8e1e325@SystematicSw.ab.ca> <63cd211e-8a4d-bfa6-5a63-aa0621af31b4@SystematicSw.ab.ca> <7cb1b594-1986-cf99-0954-8847d182d285@SystematicSw.ab.ca> From: john doe Message-ID: <75bef553-5e26-b1b8-9d0d-dd16f61983b8@mail.com> Date: Tue, 3 Aug 2021 20:20:33 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:XrVViDKef/w14WXEiEww3EG96KfAyzzk43rdu3UJwvxvK+mmNyC 45JRyGluJSDsrvIDWMCD02Q6OHOjI6No6B1B/XxhHTz9B/CL8HFF1U65wOaq/kh4DjqnEhS YcyubfiW8m4TNLjNF1mvWCWxDFlyK9xxc6GLZt24jLth5h/470XE48piiVkbcKAywEVdRql 6+nM7OJOe+D81G19TA2ag== X-UI-Out-Filterresults: notjunk:1;V03:K0:NqL8kkqII00=:bJcJqLD4FGVvn5hvbS+F6x Is0bRHoX+mXBdJ24X4GrId4iEcOBmtv+L6C4Rtiu3cjAeOq+z4/iKAfOs97O+j40NzaM8kfol 941c4MAORDlrlCfC1BvDQRWL1qu6zY2qunSRxGLo9FNZbMKOG184Y15ZRoAOr7hw0x6wsH73T 8EUrPa1HHQqHWIddFdXHAwnrb7NshqjC3OYIWblVHW2yK0vaCCHfcudW+HXEt2/Qepb2+hLpF zR5t/wHGcIRqPWTnXamubLm3Uef1EFkHN6x35n3IVC23OTAZISr6DGEiZ1LLtj6RJQr0hshEs PHFQ0Jle2ng47X8rahMxrUUWMoZBaOOGk9ATsehsKVz646K0ylGHW9eK6zxXq4czH2G2ajc4z YnID8mvnIIXBheM/2p31M+selXpct7SlxnhbDo2hoARzh1f54fhub5+i1mmo5OZphsmaOVs0+ qQV4j6kzFbDNHLnrnDtkwajAC1Zp6vuSi3EZLaYCpxdSiR9gRMJ4k7hquxKu5Dro7HBNAlA1b wWDmkfgYG3xED+LkV8ze5K8P5XTlFOrBkd+PfSB9iNoVt/rCfVBGbpuZ+QFl+8h1+M90H1NOn Dja4Xame6iMriaaj/Wy+WCEj6LVwQuk96Bl6hktcCo/Tjx8xJlbK2ho8p686cTSLaAdyZiQnq gEy7bQIy3Tc+F8xWtqyJ2hdbTMBWw4RiD4/DauUAKz52wu+UY6HuL8KQtHofDTd4zh4ExhXnS iWXzf/1MW+fcA46cp15Vlekv51dtozFaaCgL5qA9HBU9mjKkyBZ7hzfddqczZ7A+Rtq5p+V5O Vsd0UqEbAnD22jaOKsx9grRWobDCXrH25CxVSOhOkXWupoPDiKIQAC53+w1oQ0AQ9dVSfOOVb fVXrrreIJfqdLRh80zQSNl51QRoaqRqLAbKue0+EABNJIF3qTvOb/jsXdJOOdx2BvPJ74l/PQ PrMwnBENHlhX7seobC54gE0UFR+D3Zn4qwf5Gcg1jD931urRaLzELafJ+Bxh4n62WnkJLkm+1 nHThcSKISHP5J4+beQPQRmniA6FzT8GCifVyJOawUyPWhF64IL945qH0vB6SyZFaUrf1SC9hv LsPHaQfMq63dSuSJeUlP9LqQN4hSZuwTX9WkDrVAsZvhqoMfVMEB+kN9w== X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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@cygwin.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: , X-List-Received-Date: Tue, 03 Aug 2021 18:20:37 -0000 On 8/3/2021 8:12 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote= : >> "during user-initiated shutdowns, the kernel, drivers, and services are >> preserved and restored, not just restarted." > > Which was why I specifically used "shutdown /r", which is: > > /r Full shutdown and restart the computer. > > We've been advised by our admins that this command does a true and > full restart of the system, including all the kernel parts of it. > If I'm not mistaking, this command has nothing to do with "fastboot". >> You may want to check with your AD server admins about this possibility= . > > I decided to restart my computer on Saturday, while the password had bee= n changed > Thursday afternoon. Meanwhile I was perfectly able to actually _use_ my= new password > to unlock that very same Windows host, and login to different hosts (as = soon as the > new password was set, and before as well as after the reboot of my work = PC). > So the caching theory is not quite substantiated, IMO. > >> You may want to check with your AD server admins about this possibility= . > > I did! And they said: "no new policies were added and no current polici= es were changed". > > I repeat it again: my new password was working everywhere I needed to e= nter Might be better to reword than to repeat again. =2D- John Doe