Hi Volker, Thanks for all your help and I'm sorry if I'm being a nag, but I have to check all my options before moving on using nfsv4 authorization. I quickly setup a test server with the same configuration like on my prod environment, and I found that if remove gpfs module from the "vfs object" option line, I can see the permissions and get the proper permissions from the acls entries. (just like in example I sent at the begging)
If this resolves my problem, is there a reason why not using this solution? It also don't come up with what you wrote before which totally make sense to me... David On Wed, Jul 15, 2009 at 2:10 PM, Volker Lendecke <volker.lende...@sernet.de>wrote: > On Wed, Jul 15, 2009 at 02:01:43PM +0300, David wrote: > > So how can I resolve this issue? > > Add code to the gpfs module to also deal properly with posix > acls :-) > > > How come I can't see this behavior on non gpfs shares? > > Because other file systems don't need the special API calls > to get/set acls. > > > The only thing I can think off is to: changes gpfs filesystem > authorization > > to nfsv4 or all(posix and nfsv4), and change samba configuration > according. > > I don't have any nfsv4 clients, only Linux, MacOsx and windows XP which > are > > nfsv3 and smb. > > Yes, NFSv4 acls would be one way to go. This is completely > independent of whether you actually use NFSv4 as a protocol, > those ACLs are a file system thing and not primarily a > protocol thing. > > Volker > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkpduTEACgkQbsgDfmnSbrYhSwCcCnbkwrIoLF6hqbKk6942AkfP > L5YAoIqKDhUC/MZBi4+84C2pos09ILly > =Usdh > -----END PGP SIGNATURE----- > > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba