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: setup stuck on cygwin.ldif
Date: Sun, 08 Oct 2017 17:17:00 -0000	[thread overview]
Message-ID: <e3f2f44e-c5bd-6fd9-ddc2-52ffa2060a82@SystematicSw.ab.ca> (raw)
In-Reply-To: <aeb9b6b1-0ff0-1e86-f968-a5236ba8bc05@shaddybaddah.name>

On 2017-10-08 07:46, Shaddy Baddah wrote:
> I have a weird problem happening... so I have tried to update a 64-bit
> Cygwin installation on Windows 10 Pro. I closed all Cygwin processes,
> and a ps -ef is showing only the ps process itself.
> In anycase, during the install I was prompted that the file
> /usr/share/cygwin/cygwin.ldif was busy.
> I ran Process Explorer and searched for what might have the file open.
> I couldn't find anything. I clicked retry a number of times, but it
> wouldn't yield. Finally, I clicked continue. And now I'm stuck in this
> endless loop on the file:
> https://imgur.com/Nj35Y3T
> It's a animated gif, so you may have to select play in your browser. Not
> much to see, except the constant attempt to install the cygwin.ldif
> file.
> Any ideas here? I guess I'll have to kill setup... but I fear that it
> will play havoc with my install :-(

Have you tried Windows cmd OPENFILES /Query ?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2017-10-08 17:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 13:46 Shaddy Baddah
2017-10-08 14:43 ` Marco Atzeri
2017-10-08 17:17 ` Brian Inglis [this message]
2017-10-10  7:00   ` Shaddy Baddah
2017-10-10  7:21     ` Shaddy Baddah
2017-10-10 15:31       ` Jon Turney
2017-10-11 19:15 ` Ken Brown
2017-10-12  4:02   ` Resolved: " Shaddy Baddah

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=e3f2f44e-c5bd-6fd9-ddc2-52ffa2060a82@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).