Hi everyone,
I've discovered an odd problem in Samba where I can apparently create a
read-only file even though I thought I'd disabled this (primarily
because once you make the file read only, you then can't delete it
again.)
The relevant section of smb.conf:
[share]
create mask = 664
directory mask = 775
force security mode = 660
nt acl support = yes
inherit acls = yes
inherit owner = yes
If I create a file normally and try to mark it read-only it correctly
tells me 'access denied', however if I create a file elsewhere, mark it
read-only there and then copy it across to the Samba share, the file is
created in read-only mode which means I then can't delete it again.
Is this a bug in Samba or am I missing an option in my share config?
This is with Samba 3.0.21rc2.
Thanks,
Adam.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
