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 AAD83393A436
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=Ac10o1bG c=1 sm=1 tr=0 ts=61097bda
	a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17
	a=IkcTkHD0fZMA:10 a=yMhMjlubAAAA:8 a=uYT-Tk0qkVT609LjNaIA:9 a=QEXdDO2ut3YA:10
To:	cygwin AT cygwin DOT com
References:	<DM8PR09MB70959D0E3923BE1BE86F7285A5ED9 AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
	<YQenbE7ZbwzzcdQM AT calimero DOT vinschen DOT de>
	<DM8PR09MB70955B8F8E1A180504AE0718A5EF9 AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
	<YQgdnllE3OoKkVOm AT calimero DOT vinschen DOT de>
	<DM8PR09MB7095EEA62C0E5D51C704CAA5A5EF9 AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
	<DM8PR09MB7095E8E61444B71762F84138A5EF9 AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
	<771e99c7-19c5-df67-abf2-fefde0e4d7b5 AT SystematicSw DOT ab DOT ca>
	<DM8PR09MB70951F494B3C864A5D9F716EA5EF9 AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
	<57515f66-8c88-5078-8726-4883f8e1e325 AT SystematicSw DOT ab DOT ca>
	<DM8PR09MB70959B56526555CB5512B258A5F09 AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
	<63cd211e-8a4d-bfa6-5a63-aa0621af31b4 AT SystematicSw DOT ab DOT ca>
	<DM8PR09MB709556CFE9ADE552CD3FE737A5F09 AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Organization:	Systematic Software
Subject:	Re: Unable to start Cygwin64 terminal after password change
Message-ID:	<7cb1b594-1986-cf99-0954-8847d182d285@SystematicSw.ab.ca>
Date:	Tue, 3 Aug 2021 11:24:42 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
	Thunderbird/78.12.0
MIME-Version:	1.0
In-Reply-To:	<DM8PR09MB709556CFE9ADE552CD3FE737A5F09@DM8PR09MB7095.namprd09.prod.outlook.com>
X-CMAE-Envelope:	MS4xfFv/vqSYwTv7HtF70w4zHSoyJ5eK3zCpUBI4Ah1NzAzk0rMZchCPoT10tRTANO85aWv1bf9n5qWBA+gUAS9eJnywaJ5bCAe7Z52+J/AMxT7iyHYpP79K
	bRf5eHd1wW8Vbw9muOl8HDEuwy2/iRO6gHn7eHOlQTDN8JuGTFpFqWzuBxyyohEyYLPM760VIojU+6Ax73dc82yOb2lOF3mIB4Q=
X-Spam-Status:	No, score=-1161.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL,
	RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE,
	TVD_PH_BODY_ACCOUNTS_PRE, 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
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On 2021-08-03 09:50, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
>> You were "upgrading" your domain account AD data cached by cygserver.
> 
> I restarted my PC at some point with "shutdown /r"  -- I have no idea how
> cygserver can preserve its caching across this.  It's not a "fast restart".

If Fast Startup is enabled, system data could be retained, such as 
domain and/or account data, depending on the system components and 
drivers involved; it's not well documented:

https://docs.microsoft.com/en-us/windows-hardware/test/weg/delivering-a-great-startup-and-shutdown-experience 


"during user-initiated shutdowns, the kernel, drivers, and services are 
preserved and restored, not just restarted."

> The system restart did not help.

It is also possible then that there could be a problem with AD domain 
account information propagation delays, or retention of registry 
information, such that cygserver was reloaded with the same outdated 
data it had on shutdown, if your updated account information had not yet 
had sufficient time to be persisted to the ADC and propagated back.
You may want to check with your AD server admins about this possibility.

> I'd really appreciate if you could _read_ my messages before replying.
> It creates a lot of noise on the list for no reason, and it's not being
> helpful either to me or others.  Thank you for being considerate!

Your assumption is incorrect, as I carefully reread any message before 
deciding if a reply could be helpful, and I would have to make any 
assumptions that could be spurious, recheck the thread contents while 
replying to avoid making any assumptions, and cross-check what I want to 
say with information sources.
Please consider that we each have different experience that colours how 
we approach and address issues, which is why diverse project teams are 
advantageous for best and sometimes quickest responses.

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

- Raw text -