public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Unable to start Cygwin64 terminal after password change
Date: Mon, 2 Aug 2021 14:58:41 -0600	[thread overview]
Message-ID: <771e99c7-19c5-df67-abf2-fefde0e4d7b5@SystematicSw.ab.ca> (raw)
In-Reply-To: <DM8PR09MB7095E8E61444B71762F84138A5EF9@DM8PR09MB7095.namprd09.prod.outlook.com>

On 2021-08-02 12:31, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
>> I'll follow up once I have the output you've requested.
> 
> Well, my Systems people stopped cygserver for me, and I was able to open the "Cygwin64 terminal" without problems...  The machine wasn't rebooted, re-login'ed, nothing.
> 
> So cygserver was the culprit?
> 
> When I run id now, I get it all correctly, from both that very terminal:
> 
> $ id
> uid=1050182(lavr) gid=1049089(Domain Users) groups=1049089(Domain Users),555(Remote Desktop Users),545(Users),559(Performance Log Users),14(REMOTE INTERACTIVE LOGON),4(INTERACTIVE)....
> 
> and also from "bash" that I used to start from "cmd.exe" (when the terminal wouldn't open up):
> 
> C:\Windows\System32>cd \cygwin64\bin
> 
> C:\Cygwin64\bin>bash
> 
> lavr@NCBIPC9135 /usr/bin
> $ id
> uid=1050182(lavr) gid=1049089(Domain Users) groups=1049089(Domain Users),555(Remote Desktop Users),545(Users),559(Performance Log Users),14(REMOTE INTERACTIVE LOGON),4(INTERACTIVE),11(Authenticated Users),15(This Organization),4095(CurrentSession)...
> 
> Also note that my prompt is not showing anything numeric anymore...
> 
> Any clues?

All Cygwin services need to be shut down prior to running Cygwin Setup 
and they need to be restarted after Cygwin Setup completes successfully.

If Cygwin services are running while Cygwin Setup is running, Cygwin 
components in use can not be updated, and you should get a Restart to 
update prompt.

If you can not control the services, you should not run Setup: it should 
all be packaged into a script run elevated by those who have control.

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

  reply	other threads:[~2021-08-02 20:58 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 [this message]
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
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=771e99c7-19c5-df67-abf2-fefde0e4d7b5@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).