![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 13/04/2019 14.24, Andrei Borzenkov wrote:
13.04.2019 13:36, Carlos E. R. пишет:
...
Yes, I thought of that this morning, but it is not my doing.
So what? You asked why you cannot access this directory and this is the answer.
Sigh. You always have to be so blunt? It was not my doing, which explains why I did not understand what was going on. I had not written that permission. What my mind saw was the permissions I had written.
The command I used to set ACLSs was:
setfacl -m u:wwwrun:rx
The file was copied from another directory, by rsync.
Original file:
cer-g@Isengard:~/F_Videos/1_Almacenar> getfacl Conviction # file: Conviction # owner: cer-g # group: cer # flags: --t user::rwx user:wwwrun:r-x group::rwx <===== mask::rwx other::r--
copied file:
cer-g@Isengard:~/F_Videos/1_Almacenar> cer-g@Isengard:~/F_Videos/3_MyBook_Videos> getfacl Conviction # file: Conviction # owner: cer # group: cer user::rwx user:wwwrun:r-x group::--- <==== mask::rwx other::r--
How has the ACL changed ?
ACL did not change. Group permissions changed. Trivial answer is umask. Less trivial answer is default ACL on parent directory. You are in the best position to debug it as only you can reproduce it in your environment.
Sigh. The group permission did not change, as shown by "ls -l". The ACL group permission changed. And no, I still have no idea why rsync changed, or did not copy, the group ACL. Do you?
(the 't' I deleted yesterday)
The command to copy the files was:
cer@Isengard:~> time rsync --archive --acls --xattrs \ --hard-links --sparse --stats --human-readable \ --checksum /data/waterhoard/Fusion/Videos/1_Almacenar/ \ /data/My_Book/Fusion/Videos/
I told rsync to keep the ACLS, but it has modified them.
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)