From: Linda Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: Unknown+User Unix_Group+505 on smb shares in a domian
Date: Thu, 29 Sep 2016 08:38:00 -0000 [thread overview]
Message-ID: <57ECA908.9010402@tlinx.org> (raw)
In-Reply-To: <20160928180456.GA1128@hdmetxxxx33004g.AD.UCSD.EDU>
Wayne Porter wrote:
> The server that the W: drive is mapped on is not using domain accounts. As far as I know,
> all Linux servers we have are running local accounts. Is there something I can set in
> my local /etc/passwd to convince Cygwin to map it to my user account?
---
If the linux servers are not exporting files under the domain account,
then they files are not part of the 'domain' but owned only by the username
on that specific linux-machine. It sorta sounds like the linux server may
not even be in the domain -- in which case mentioning domains only confuses
the issue.
Essentially you have a bunch of users on different machines that
aren't sharing their files under any common (or shared) security authority
(like a single domain). Until you persuade the owners of those linux machines
to move the linux machines under a common security authority (like a windows
domain) and moving the user accounts into the domain. Each local account
would have to be moved to a domain account with the files under each
machine-local account being moved (or "chown'ed") to the new, corresponding
domain account).
This is an organizational problem that has nothing to do with
cygwin, but whether windows and linux machines are using domain or machine-local
security. Until your linux machines and their local user become
part of the domain, you can't expect any "write" privileges granted to
you under the domain to work on the linux machines.
--
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 prev parent reply other threads:[~2016-09-29 5:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 23:59 Wayne Porter
2016-09-28 17:55 ` Linda Walsh
2016-09-28 19:52 ` Wayne Porter
2016-09-28 21:44 ` Andrey Repin
2016-09-28 22:59 ` Wayne Porter
2016-09-29 20:35 ` Andrey Repin
2016-09-29 8:38 ` Linda Walsh [this message]
2016-09-29 19:35 ` Wayne Porter
2016-09-30 5:05 ` Andrey Repin
2016-10-01 22:38 ` Wayne Porter
2016-10-02 23:49 ` Linda Walsh
2016-10-03 1:28 ` Wayne Porter
2016-10-02 23:44 ` Linda Walsh
2016-10-02 23:58 ` Wayne Porter
2016-10-03 6:33 ` Linda Walsh
2016-09-29 15:22 Roland Schwingel
2016-10-19 11:45 ` Corinna Vinschen
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=57ECA908.9010402@tlinx.org \
--to=cygwin@tlinx.org \
--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).