Did that. Using MS Word to modify another file didn't produce an ACL for
the file this time, but it didn't set the archive bit either.
Point blank: Should proper expected archive bit behavior be functional
with Samba regardless of the underlying application? (i.e. Notepad and
Wordpad work while MS Word doesn't)
Jeremy Allison wrote:
On Mon, Sep 11, 2006 at 03:20:45PM -0400, Aaron Kincer wrote:
Thanks to all that have helped so far.
I now have a test server running on Ubuntu 6.06 and Samba 3.0.22. I also
configured ACL and user_xattr on the filesystem running the shares. But
now I have very strange behavior that I hope someone has a clue about.
User smith can open two files (foo.txt and faa.txt) with Notepad,
Wordpad and Microsoft Word. The behavior for all three is different:
foo.txt
Notepad: Can open and modify the file. Correctly sets the archive bit.
Wordpad before Word mod: Can open and modify the file. Correctly sets
the archive bit.
Wordpad after Word mod: Can open but cannot modify the file (access
denied error). Cannot set the archive bit since access denied.
Word: Can open and modify the file. Does not correctly set the archive
bit. Using word created an ACL where none existed before (ACL was
enabled AFTER file was initially created)
faa.txt
Notepad: Can open and modify the file. Correctly sets the archive bit.
Wordpad: Can open and modify the file. Correctly sets the archive bit.
Word: Never used to modify.
Set :
map archive = no
map hidden = no
map system = no
if you have
store dos attributes = yes
set.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
