From: Andrey Repin <anrdaemon@yandex.ru>
To: L A Walsh <cygwin@tlinx.org>, cygwin@cygwin.com
Subject: Re: win dirs don't handle lack of inherited rule(?): getfacl + tar dir Warning: Cannot acl_to_text: Invalid argument
Date: Sun, 10 Mar 2019 22:50:00 -0000 [thread overview]
Message-ID: <951349031.20190311013719@yandex.ru> (raw)
In-Reply-To: <5C853D99.3080401@tlinx.org>
Greetings, L A Walsh!
> On 3/10/2019 6:27 AM, Andrey Repin wrote:
>> Greetings, L A Walsh!
>>
>>> On 3/8/2019 4:15 AM, Corinna Vinschen wrote:
>>>> On Mar 7 19:35, L A Walsh wrote:
>>>>> I ran tar on another directory and got a huge number**
>>>>> of these:
>>>>> tar: rules: Warning: Cannot acl_to_text: Invalid argument
>>>>> tar: adblockplus: Warning: Cannot acl_to_text: Invalid argument
>>>>> tar: autopager: Warning: Cannot acl_to_text: Invalid argument
>>>>> tar: bookmarkbackups: Warning: Cannot acl_to_text: Invalid argument
>>>>> ---
>>>> Can you please provide the cacls or icacls command creating
>>>> a directory that allows to reproduce the issue?
>>
>>> I doubt that area of my disk has ever been manipulated by
>>> cacls or icacls. That's in my roaming profile.
>>
>> It's not about manipulation, it's about current state.
>>
>> icacls is a Windows equivalent of POSIX's setfacl/getfacl.
> ---
> I know. I meant manipulate in the sense of
> handling something with dexterity and finesse. -- which
> is a different connotation or sense of the word than when
> talking about one person manipulating another.
> How would _you_ create these symptoms if you don't know
> how they got that way -- just that they exist that way.
By running the dump of icacls locally on a given directory.
The output is the same fomat as input, much like it is for get/setfacl.
> Furthermore. I'm pretty sure that a person would not
> be able to create that symptom with icacls (or the deprecated cacls).
You'd be surprised.
> I would not doubt that icacls would refuse to create
> mis-ordered ACL's, for example.
Again, you'd be surprised.
> I.e. its likely a non-windows
> program or odd interaction between one and windows.
> That's why I pointed out that besides cygwin creating acl's that
> explorer will complain about, the roaming profile has also received
> profiles from a samba server on linux (with a different permission
> structure).. Its unclear what permissions are copied then and how
> they are mapped.
--
With best regards,
Andrey Repin
Monday, March 11, 2019 1:35:53
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:[~2019-03-10 22:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 3:36 L A Walsh
2019-03-08 12:15 ` Corinna Vinschen
2019-03-10 10:48 ` L A Walsh
2019-03-10 11:20 ` Corinna Vinschen
2019-03-10 13:35 ` Andrey Repin
2019-03-10 16:38 ` L A Walsh
2019-03-10 22:50 ` Andrey Repin [this message]
2019-03-10 23:15 ` L A Walsh
2019-03-10 14:09 ` Brian Inglis
2019-03-12 15:45 ` L A Walsh
2019-03-12 16:36 ` Corinna Vinschen
2019-03-13 2:22 ` L A Walsh
2019-03-13 9:19 ` Corinna Vinschen
2019-03-13 9:32 ` Corinna Vinschen
2019-03-13 11:34 ` Corinna Vinschen
2019-03-15 2:46 ` L A Walsh
2019-03-15 9:17 ` Corinna Vinschen
2019-03-15 12:25 ` Brian Inglis
2019-03-15 13:34 ` Corinna Vinschen
2019-03-15 14:46 ` L A Walsh
2019-03-15 14:52 ` 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=951349031.20190311013719@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).