3

Ownership doesn't matter. The only kind of access automatically granted to the owner is the ability to edit the access list (in case the access list itself doesn't grant that), but it doesn't otherwise affect whether you can read or write the files themselves. To actually achieve unlimited access, you need to add "Everyone" to the access list and ...


2

Short answer: you haven’t given execute permission to anybody but the file’s owner.  The mode is currently 4764.  The last two digits have to be 5 or 7 for it to be executable by others. Use 4755.  It’s rare that you want a file to be writable by people other than the owner.  There are cases where you want this, but the default should be NN44, NN55 or NN11 (...


2

This is a bug in older WSL implementation which keeps pinning all the opened files but forgets to track them when they're closed. This is fixed in most recent versions of WSL and WSL2. As a temporary hack, one can cp to target and rm the old source Please refer to the GitHub issues for WSL Project


1

You will need to define "default ACLs" using setfacl. This works not only for named user/group ACLs, but also for the basic unnamed permission bits: setfacl -d -m "u::rwx,g::rwx,o::-" parentdir Note that you cannot force new files to be executable; even if the ACL grants +rwx, the newly created file will still have a mask:: entry ...


Only top voted, non community-wiki answers of a minimum length are eligible