Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have implemented Samba on our campus. Accounts and groups are maintained in an LDAP DIT. Access to shared folders is group based. Our Samba share definitions have something like:

valid users = +share_a-rw, +share_a-r

This allows users from read/write and read groups to have access. On the file system, the share group owner is share_a-rw (the group with read/write) access, and read access is provided by a POSIX file ACL. Default ACLs are set for the read group as well, so new file created in the folder get the ACL. The folder is setGID so the main group is also propagated.

The system has been working well, but I noticed that if an end user "moves" a file from one share to another rather than copying, the file does not contain the ACL for the read group. We are using MS DFS links to make all our file servers appear as a single large server.

I am wondering if there is some setting in Samba that can make the behavior emulate a copy rather than a move. Has anybody had any experience with this issue?

Thanks, Carl

share|improve this question
Moving file on a non-DFS source/target works as expected? – Greg Askew Mar 8 '13 at 14:49
If I move from file server "A" to file server "B", Samba seems to do a copy and the ACLs are created as I would expect. If I move from a share on server "A" to another share on server "A", samba performs a move, and the ACLs are not set as expected. – Carl Mar 9 '13 at 15:42
That sounds like expected behavior to me. – Greg Askew Mar 9 '13 at 15:48

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.