This post is quite old, so I assume this is no longer a problem... However, others searching discussions may be interested some of the answers.
>>the application creates folders to store metadata, but they come up with a >>000 permission rather than the 777 I'd expect. When mounting a CIFS or SAMBA share you can set the permissions: EXAMPLE: pfexec mount -F smbfs -o fileperms=777 -o dirperms=777 //username at sambaserver/share /mnt Alternatively, when connecting to a SMB share both authentication and permissions must be satisfied. So, the 'username' portion of the string above provides data for authentication, while the 'fileperms' and 'dirperms' portions provide permission info...along with the integrated zfs perms. Solaris CIFS, I understand, does not provide for a 'null' (using no username/password) authentication. So, clients have to authenticate to the solaris server if in workgroup mode, and to AD or NIS if in directory-integrated mode. As far as I know, as of snv_123, opensolaris cifs server lacks any credential caching ability that would temporarily allow the CIFS server to authenticate or accept the client's token if the AD or other directory server were temporarily unavailable for some reason. I may be wrong... but if so I'd like to know how to set up credential-caching... Gordo -- This message posted from opensolaris.org
