Geo-replication uses this option to identify itself as an internal client
On Sun, Oct 13, 2019 at 11:41 AM Amar Tumballi wrote:
>
>
> On Fri, Oct 11, 2019 at 5:05 PM Mohit Agrawal wrote:
>
>> Hi,
>>
>> Yes, you are right it is not a default value.
>>
>> We can assign the client_pid only while v
On Fri, Oct 11, 2019 at 5:05 PM Mohit Agrawal wrote:
> 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
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
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
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
