On Tue, Feb 25, 2014 at 03:13:13PM -0500, Brad Childs wrote: > As a follow on questions - will libgfapi allow/deny file access based > on owner/group/mode of a file against the user accessing libgfapi?
Yes, it should. The uid/gid (and auxiliary groups) are sent in the GlusterFS RPC/AUTH header. The storage servers (well, brick processes) use this information to allow/deny access. Niels > > > -bc > > > ----- Original Message ----- > > From: "Gong XiaoHui" <xhg...@wind.com.cn> > > To: "Niels de Vos" <nde...@redhat.com>, "Vijay Bellur" <vbel...@redhat.com> > > Cc: gluster-devel@nongnu.org > > Sent: Thursday, February 20, 2014 6:39:56 PM > > Subject: [Gluster-devel] 答复: how to use libgfapi with non-root user > > > > Thanks,I stop and start the volume, it works ok. > > The right step is: > > 1. add ” option rpc-auth-allow-insecure on” to *.vol file > > 2. set <volname> server.allow-insecure on > > 3. stop and start the volume > > > > -----邮件原件----- > > 发件人: Niels de Vos [mailto:nde...@redhat.com] > > 发送时间: 2014年2月21日 1:05 > > 收件人: Vijay Bellur > > 抄送: Gong XiaoHui; gluster-devel@nongnu.org > > 主题: Re: [Gluster-devel] how to use libgfapi with non-root user > > > > On Thu, Feb 20, 2014 at 09:35:00PM +0530, Vijay Bellur wrote: > > > On 02/20/2014 02:33 PM, Gong XiaoHui wrote: > > > >Hi, > > > > > > > > This is a programmer from china, now I have a problem with > > > >libgfapi(V3.4.2). My application run as non-root user uses a api called > > > >glfs_init, but it return -1. > > > > > > > > From the internet I find a solution, add” option > > > >rpc-auth-allow-insecure on” into the vol file on my gluster system, then > > > >the glfs_init return 1, it does’t work ok either. > > > > > > > >I need some help to resolve this problem, expect your reply. Thank you > > > >very much. > > > > > > > > > > Have you tried this? > > > > > > gluster volume set <volname> server.allow-insecure on > > > > > > This would also be needed in addition to editing glusterd's volume file. > > > > In case this is not working yet, you should probably stop and start the > > volume where you changed the server.allow-insecure setting. > > > > HTH, > > Niels > > > > _______________________________________________ > > Gluster-devel mailing list > > Gluster-devel@nongnu.org > > https://lists.nongnu.org/mailman/listinfo/gluster-devel > > _______________________________________________ Gluster-devel mailing list Gluster-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/gluster-devel