Turning it on its head then, set ACLS for the full read-write share, and set the local perms to 700. Then set the flags on the original mount to honour acls, and the flags on the second mount to *not* honour acls.
Then set hide unreadable=yes for the second mount. Maybe the "nt acl support" option will help. Maybe a different way to approach the problem. YMMV -=Andrew -----Original Message----- From: Allen Chen [mailto:ac...@harbourfrontcentre.com] Sent: Tuesday, August 25, 2009 7:40 AM To: Andrew Masterson Cc: samba@lists.samba.org Subject: Re: [Samba] Veto files question Andrew Masterson wrote: > hide unreadable = yes > > is the closest I can think of. You could then set perms to something > like 400 and only owners will be able to read their own files. > > -=Andrew > > Thank you, Andrew. Changing the perms is not the solution. This is what I want to do: I have a public share. Everybody can read,write and modify files within this share. This works perfect. * I want to create another 'share' in smb.conf pointing to the same folder. * When a user mounts this share, he will only see the files belongs to his. I think Samba should have the power to filter it. Any idea? Allen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba