From: Andrey Repin <anrdaemon@yandex.ru>
To: L A Walsh <cygwin@tlinx.org>, cygwin@cygwin.com
Subject: Re: continued acl problems
Date: Fri, 07 Sep 2018 21:35:00 -0000 [thread overview]
Message-ID: <164180157.20180908002635@yandex.ru> (raw)
In-Reply-To: <5B92EA14.1030507@tlinx.org>
Greetings, L A Walsh!
> In all of these cases it appears that the problem is with directories.
> At first thought it was related to presence of 'TRUSTED USER'
> But I saw some 'flakeyness' on domain ID's,
> where I saw it display the correct text for them,
> but scrolling down to look for problems, and back up had the
> permissions dialog showing the raw numbers for my domain ID's, but
> scrolling again showed them as Domain\ID.
Do you have cygserver running?
> So that's something to consider -- if there is a momentary flake
> in the resolution, it might cause a prob....just tried those files
> again. the "tmp/05" and "tmp/51..."
> No errors.
> Did something else change besides these probs you looked at?
> I have to stress...I've never seen the Cannot_acl_to_text
> message before my reporting it a week or so ago....
> saw instances in use of 'tar' and 'rsync' at this point.
> I have seen similar messages out of rsync copying from a windows
> dir to a samba dir -- I figured local ID didn't exist on the
> remote samba dir.
> But have never seen it going between win-directories on the same
> machine...that's the new "problem", with current symptoms seeming
> to be limited to directories (maybe due to 2 acls)...
> Have never had these msgs going from win<->win on same
> machine.
--
With best regards,
Andrey Repin
Saturday, September 8, 2018 0:25:37
Sorry for my terrible english...
--
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:[~2018-09-07 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 21:14 L A Walsh
2018-09-07 21:35 ` Andrey Repin [this message]
2018-09-07 23:08 ` L A Walsh
2018-09-08 0:35 ` Andrey Repin
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=164180157.20180908002635@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=cygwin@tlinx.org \
/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).