[Gluster-devel] CfP: Software Defined Storage devroom at FOSDEM 2020

FOSDEM is a free software event that offers open source communities a place to meet, share ideas and collaborate. It is renown for being highly developer- oriented and brings together 8000+ participants from all over the world. It is held in the city of Brussels (Belgium). FOSDEM 2020 will take

[Gluster-devel] Query regards to expose client-pid to fuse process

Hi, I have a query specific to authenticate a client based on the PID (client-pid). It can break the bricks xlator functionality, Usually, on the brick side we take a decision about the source of fop request based on PID.If PID value is -ve xlator considers the request has come from an inte

Re: [Gluster-devel] Query regards to expose client-pid to fuse process

On Fri, 11 Oct 2019 at 14:56, Mohit Agrawal wrote: > Hi, > > I have a query specific to authenticate a client based on the PID > (client-pid). > It can break the bricks xlator functionality, Usually, on the brick side > we take a decision about the >source of fop request based on PID.If P

Re: [Gluster-devel] Query regards to expose client-pid to fuse process

Hi, Yes, you are right it is not a default value. We can assign the client_pid only while volume has mounted after through a glusterfs binary directly like /usr/local/sbin/glusterfs --process-name fuse --volfile-server=192.168.1.3 --client-pid=-3 --volfile-id=/test /mnt1 Regards, Mohit Agrawal