From: john doe <johndoe65534@mail.com>
To: cygwin@cygwin.com
Subject: Re: Unable to start Cygwin64 terminal after password change
Date: Tue, 3 Aug 2021 20:20:33 +0200 [thread overview]
Message-ID: <75bef553-5e26-b1b8-9d0d-dd16f61983b8@mail.com> (raw)
In-Reply-To: <DM8PR09MB7095A64AC6B821349856E0D9A5F09@DM8PR09MB7095.namprd09.prod.outlook.com>
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 been 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 policies were changed".
>
> I repeat it again: my new password was working everywhere I needed to enter
Might be better to reword than to repeat again.
--
John Doe
next prev parent reply other threads:[~2021-08-03 18:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 21:09 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-07-31 21:46 ` Brian Inglis
2021-08-02 8:06 ` Corinna Vinschen
2021-08-02 15:12 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 16:30 ` Corinna Vinschen
2021-08-02 16:49 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 18:31 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 20:58 ` Brian Inglis
2021-08-02 21:38 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-03 0:38 ` Brian Inglis
2021-08-03 1:47 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-03 15:23 ` Brian Inglis
2021-08-03 15:50 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-03 17:24 ` Brian Inglis
2021-08-03 18:12 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-03 18:20 ` john doe [this message]
2021-08-04 10:03 ` Andrey Repin
2021-08-03 11:24 ` Corinna Vinschen
2021-08-03 15:07 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 15:16 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-01 16:57 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-01 17:23 ` René Berber
2021-08-01 19:28 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-01 19:53 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 14:59 ` Andrey Repin
2021-08-02 15:14 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 15:20 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 21:21 ` Andrey Repin
2021-08-02 21:39 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
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=75bef553-5e26-b1b8-9d0d-dd16f61983b8@mail.com \
--to=johndoe65534@mail.com \
--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).