Bugzilla – Bug 437765
mv command does not inherit ACLs on moved files
Last modified: 2008-10-29 06:08:43 UTC
When moving a file from e.g. $HOME without ACLs to a collaboration share which uses ACLs for permission management, the default ACLs are not inherited. This makes the usage of ACLs pretty much useless unless the users are forbidden to move files... I will attach the script we use to set acls recursively on a folder in order to have proper permissions.
Created attachment 247179 [details] shell script used to prepare a collaboration directory
Created attachment 247181 [details] shell script to strip all ACLs and extra attributes from a directory
This is not a new behavior but exists at least since openSUSE 10.2. Other basic commands seem to work, especially copying.
isn`t that the same even on windows - i.e. moving files within the same partition doesn`t make those files have the correct acl`s
I have no idea about Windows... All I care is unixoids in a Samba network :) If the ACL implementation really copies bad Windows behavior to the point that it omits default ACLs upon moving, I'd very much vote for an additional option for the command. Would that be possible? I am thinking about something like mv --inherit-acls
"The mv command conceptually moves filesystem objects, and doesn't create new objects. Thus default acls are not inherited, just as the umask has no effect. This behavior is by design." Bug 120975 Closing as INVALID. *** This bug has been marked as a duplicate of bug 120975 ***