i have problem with mentioned keyword, and have created a simple test case to show that. i'm talking about home share with default options used except 'hide unreadable' which was set to 'Yes'. on linux client: mkdir tmp tmp/normal tmp/restricted on WXP client: cd tmp && dir (get normal and restricted directories) then, on linux: chmod go-rwx tmp/restricted on WXP: dir (gives ONLY normal directory) cd restricted (WORKS) dir (OK, gives restriced content) can anyone explain why is such behaviour occuring? and am i doing something wrong here ? when i set 'hide unreadable' to 'No' everything works nice and smooth.
samba uses the filesystem permission execution bits to store that type of informations. Just look at the acl howto part in samba docs, and the 'acl' keywords in 'man smb.conf'
i think you have missed the point. what has ACL support to do with it? for this simple testcase standard POSIX permissions are enough to show that there is something wrong with the option. could you please elaborate on what you said ?
maybe I misunderstood your intentions: is this ralated to 'inherit permissions' and/or 'map {archive,hidden,system}'? what are the remote (and local) user credentials?
