Hello all I have had some dubious experiences using the ACL features of Samba 3.0.0
At present I have rolled-back our production servers to 2.2.8a (--with-acl ) but I hope that they will be ironed-out by 3.0.1 and I can upgrade again.
The problems manifested themselves in two client applications, CVS and Quickbooks althouth there was only 24'ish hours of live use before the decision was made to roll-back.
The CVS problem went thus.
CVS repositories held on an ext3+acl partition, access by samba with "force-user=someuser" and "valid [EMAIL PROTECTED]"
CVS working directories held on [homes] share
When performing a "cvs edit" or "cvs unedit" the permissions of the files were not being set to read-only correctly. It was possible to set these permissions using the standard Windows file property dialogs.
Since much of our work uses CVS intensively, this would not do. This behaviour ocurred whether or not oplocks were employed.
The Quickbooks problem was nasty but I think I could have got around it with options.
The kernel is 2.4.21 +ea+acl The shares are exported via patched NFS for version 3 NFS clients only.
2.2.8a has plenty of quirks with ACL's enabled but I won't go into those now.
--
========================================= Ben Tullis IT Manager
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
