setting 'profile acls = yes' on a share causes the share contents to appear with
DOS Read-only attributes.
path = /tmp/share
create mask = 0770
directory security mask = 0770
profile acls = yes
browseable = yes
guest ok = no
read only = no
This behavior started in 3.0.11 and I believe its due to the following changes:
I can confirm that backing out these changes in 3.0.14a fixes this behavior.
it probably just causes your *folders* to be r/o, right? Do you have any problem
with this ?
Anyway - There seem to be problems with r/o attributed "special" folders and
some applications, which don't expect this. It might be a good idea to store the
r/o bit in extended attributed when store dos attributes are enabled. That would
not be a solution for systems which don't have xattrs but I don't see a better
way to do this.
arrg, no you have a more generic problem. Do not set profile acls on a normal
share, doing this is broken by design. profile acls may just be used for profile