public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Permissions Problems
Date: Mon, 30 May 2016 16:35:00 -0000	[thread overview]
Message-ID: <20160530104002.GD6659@calimero.vinschen.de> (raw)
In-Reply-To: <e5d9c7bf-a55c-fdec-78f5-92c956be383d@huarp.harvard.edu>

[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]

On May 16 10:13, Norton Allen wrote:
> 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?

It's not the username per se, it's the fact that the db-only setting
doesn't allow o create valid passwd/group entries for your user.

So, yes.  In your scenario you should ideally revert back to "files db"
and create minimal /etc/passwd and /etc/group files.

/etc/passwd may contain only your own user account.  /etc/group
only the domain groups you're member of.  Everything "special" or
"local" will be picked up just fine by Cygwin then.  If there are
also files on your machine owned by some other domain user, it might
be helpful to add that account to /etc/passwd, too.


HTH,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-05-30 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 14:13 Norton Allen
2016-05-30 16:35 ` Corinna Vinschen [this message]
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=20160530104002.GD6659@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).