If I remember correctly, someone asked a similar question a little while
ago on the list.
What you are observing is probably due to the behaviour of the way
certain applications write to files. Some windows applications
move/remove the old file, and create a new file with the same filename
when a user "saves" an open file. Thus, you are losing the ACL on the
file, so to speak.
You could overcome this problem by setting a default ACL for the user
group on the parent directory of any files you share. That way, new
files are created with the needed ACLs to allow other users in the group
to modify the files. Thus, files which are edited and "saved" by
software of said behaviour will have the correct ACLs.
hope this helps,
On Fri, Jun 07, 2002 at 09:37:11AM -0400, Ken D'Ambrosio wrote:
> I'm not sure if this is a Samba issue or an XFS issue, but for various
> users, on files that are commonly shared by others, the ACLs change in
> weird ways, with no action (other than saving the file) on the user's
> - One user, upon saving the file, has the ACL (but not the "stock" Unix
> permissions) change to no permissions at all for group.
> - Another two users, upon saving, have the Unix permissions change to
> the equiv. of "chmod o-w".
> Any idea what might cause this to be happening, or where I should look
> to find more info? It's entirely reproducible, and, right now, I have a
> script running that "chmods" the files every couple seconds -- hack in
> the extreme. Unless I figure something out, I'll probably start by
> disabling ACLs in Samba, and see if the problem goes away.
> Ken D'Ambrosio
> Sr. SysAdmin,
> Xanoptix, Inc.
Ian Cumming, ian@xxxxxxxxxxxxxx
"The number of Unix installations has grown to 10, with more expected."
-- The Unix Programmer's Manual, 2nd Edition, June, 1972