From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Unknown+User Unix_Group+505 on smb shares in a domian
Date: Wed, 19 Oct 2016 11:45:00 -0000 [thread overview]
Message-ID: <20161019113809.GD4801@calimero.vinschen.de> (raw)
In-Reply-To: <7e5a95d3-37aa-1efd-f7fb-f88f5683b561@onevision.de>
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
On Sep 29 10:38, Roland Schwingel wrote:
> Hi to all..
>
> I have the very similar problem.
>
> >> > I can't do anything, it just becomes an inconvenience.
> >> > d---r-x---+ 1 NT SERVICE+TrustedInstaller NT
> SERVICE+TrustedInstaller 0 Sep 26 08:50 c
> >> > drwxrwx---+ 1 Administrators Domain Users 0 Sep
> 14 11:57 i
> >> > drwxrwx---+ 1 SYSTEM SYSTEM 0 Sep 26
> 12:55 j
> >> > drwxrwx---+ 1 Administrators Domain Users 0 Sep
> 27 07:55 m
> >> > drwxr-xr-x 1 root ieng6_root 0 Jul
> 12 04:04 v
> >> > drwxrwxr-x 1 Unknown+User Unix_Group+505 0
> Sep 21 09:41 w
> >> > drwxrwxr-x 1 Unix_User+99 Unix_Group+101 0
> Sep 21 15:20 y
> >> >
> >>
>
> > You can tell your IT dep to pull their asses up and join all servers > to
> AD. That would be a much more straightforward solution.
>
> My servers (linux with samba 4.4) are joined to the domain. An older
> cygwin 1.7 does not show this problem. Presently this problem hinders
> myself for quite some while to move to a newer cygwin version.
>
> In my case it shows something like:
> -rwx------ 1 Unix_User+roland Unix_Group+develop 25 Sep 11 13:13 test.png
>
> And some file operations fail in cygwin (2.4.1 - this was my last version I
> have tried) - mostly writting to the files, while writting to the files from
> windows directly works...
>
> Any help would also be appreciated.
There is a server-side solution for this problem, outlined in the docs:
https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nfs
https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-samba
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 --]
next prev parent reply other threads:[~2016-10-19 11:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 15:22 Roland Schwingel
2016-10-19 11:45 ` Corinna Vinschen [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=20161019113809.GD4801@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).