[Samba] ACL and copy/move file

Tony Earnshaw tonye at billy.demon.nl
Mon May 2 07:41:36 GMT 2005

man, 02.05.2005 kl. 00.34 skrev Andi:

> Inside a single directory, I have 2 subdirectories:
> dirname=working
> (root.root rwsrwsr-x)
> user::rwx
> group::rwx
> user:user1:rwx
> group:group1:rwx
> default:user::rwx
> default:group::rwx
> default:user:user1:rwx
> default:group:group1:rwx
> dirname=controlled  (root.root rwsrwsr-x)
> user::rwx
> group::rwx
> group:group2:rwx
> default:group:group2:rwx
> default:user::rwx
> default:group::rwx
> The idea being that files from the 'working' directory get copied/moved 
>   into the 'controlled' area, and are then read-only to everybody 
> (except for group2).
> When a file is *copied* from 'working' to 'controlled' the default acl 
> of 'controlled' is applied.
> If the file is *moved*, the acl's that are on the file in the 'working' 
> directory, are also transferred - effectively allowing that file to be 
> modified.
> With WinXP, the permissions from the destination directory are applied 
> to the file, whether it is copied or moved. I believe the same is true 
> on WinNT.
> Is this a bug with Samba?
> (Using Samba 3.0.14a)

Last week I asked a tangential question. The answer was, naturally,
that, given a dual environment Windows/Unix, the underlying Unix rules
for a filesystem will always apply to files on the Samba server.

In your case (as in mine) what you're seeing is the normal Unix cp/mv
behavior and I wouldn't call it a Samba "bug". I suppose a routine could
be written into samba to counter this, the developers would have to
answer that.


Nothing sucksseeds like a pigeon without a beak ...

mail: tonye at billy.demon.nl
They'll love us, won't they? They feed us, don't they? ...

More information about the samba mailing list