From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
To: cygwin@cygwin.com
Subject: Resolved: Re: setup stuck on cygwin.ldif
Date: Thu, 12 Oct 2017 04:02:00 -0000 [thread overview]
Message-ID: <30c49c8f-9b30-a77f-5a32-a43556f2ff0c@shaddybaddah.name> (raw)
In-Reply-To: <8b9ba941-37da-fe2c-32c3-7ac5037a8b4f@cornell.edu>
Hi,
On 12/10/17 06:15, Ken Brown wrote:
> On 10/8/2017 9:46 AM, Shaddy Baddah wrote:
>> Hi,
>>
>> 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
>
> The progress bar shows that your disk is almost full. Could that be the
> problem?
Thanks for your concern.
I've found the problem. I haven't been vigilant in my
installation/update procedure. And I've paid a high price.
I normally only ever install as a "software user", portapps, that I have
to "runas" to obtain a command prompt to. From that command prompt I run
the setup.exe, and all the files end up owned by portapps, not my normal
desktop user.
I instituted this policy more than a decade ago when I accidentally
corrupted my install, by running a script or something like that, that
deleted some "system files" due to a path issue. My desktop user has no
permissions to modify any installed Cygwin files other than in their
/home directory. The policy could work using a privileged user, but I
also seek to avoid being dependant on using a privileged user on my
desktop.
Well, I've corrupted my install now by accidentally running an update
last month as the elevated administrator user. A bunch of directories
are now owned by the privileged user, and the portapps user can't
modify the directories.
I'll solve my own mess now. Thanks again.
--
Regards,
Shaddy
--
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
prev parent reply other threads:[~2017-10-12 4:02 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
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 ` Shaddy Baddah [this message]
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=30c49c8f-9b30-a77f-5a32-a43556f2ff0c@shaddybaddah.name \
--to=lithium-cygwin@shaddybaddah.name \
--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).