From: Norton Allen <allen@huarp.harvard.edu>
To: cygwin list <cygwin@cygwin.com>
Subject: Permissions Problems
Date: Mon, 16 May 2016 14:13:00 -0000 [thread overview]
Message-ID: <e5d9c7bf-a55c-fdec-78f5-92c956be383d@huarp.harvard.edu> (raw)
I have seen problems similar to those reported in "RE: Possible issue
with newest version of git (v 2.8) under Cygwin", but I did not want to
hijack that thread.
For me, the problems have been elusive. Scripts that used to work would
fail as created directories had bad permissions, but I didn't have time
to sort them out. In the last week, I finally had time to read through
the documentation on the ntsec page and try some tests, and of course
now I'm having trouble reproducing the problems. You'd think that was a
good thing, right?
I had been using /etc/passwd from mkpasswd, and based on recommendations
here, I modified nsswitch for passwd: db. This seemed to work fine, and
I decided I was all set.
Then Windows update rebooted over the weekend, and nothing worked, and
returning to 'files' resolved the problem.
The exacerbating factor here is that I have a laptop connected to my
work domain, but we use cached windows credentials when we are not on
the work LAN (like at home over the weekend). In this scenario, cygwin
was apparently unable to determine my username, and hence was unable to
locate my home directory. The username is apparently cached successfully
if I reboot at work and then go offline, but not if I reboot offline.
Does this mean I need to stay with 'passwd: files db' for the
foreseeable future, or is it possible to find the username in this scenario?
--
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
next reply other threads:[~2016-05-16 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 14:13 Norton Allen [this message]
2016-05-30 16:35 ` Corinna Vinschen
2016-05-30 16:51 ` Norton Allen
-- strict thread matches above, loose matches on Subject: below --
2001-09-24 6:39 permissions problems Serge Pluess
2001-09-20 4:23 Jean Barata
2001-09-20 7:14 ` Larry Hall (RFK Partners, Inc)
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=e5d9c7bf-a55c-fdec-78f5-92c956be383d@huarp.harvard.edu \
--to=allen@huarp.harvard.edu \
--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).