[Gluster-users] help, avoid glusterfs client from occuping rsync port 873

[符永涛]

I have finished a patch on my local repo based on glusterfs3.3.0.5rhs
source rpm. The patch export client-bind-insecure option to fuse
mount.
To use it the command would be like the following:
mount -t glusterfs -o client-bind-insecure <server>:<volume> <mountpoint>
This involves very few changes on glusterfs client side and works for me now.
In my client machine there're several volumes and every volume has
tens of bricks and local port always conflicts.

2013/3/12, John Mark Walker <johnmark at redhat.com>:
> Was looking through your steps - it would be interesting to see if there are
> any unforeseen ramifications from doing this.
>
> Hoping to see some others chime in who've tried it.
>
> -JM
>
>
> ----- Original Message -----
>> Gives above steps are too complex and it's not easy to maintain
>> volume
>> files especially if the volume backend brick changes. I intend to
>> make
>> it a patch and only make it configurable throw mount option on the
>> client side. Any body agree with me?
>> Thank you.
>>
>> 2013/3/12, 符永涛 <yongtaofu at gmail.com>:
>> > Finally I find the answer though it's not very convinient but
>> > doable.
>> > 1 sudo gluster volume set <volume> server.allow-insecure on
>> > 2 get the volume file from glusterfs backend server
>> > the file is <volume>-fuse.vol
>> > 3 edit the volume file add option client-bind-insecure and set it's
>> > value to on for every protocol/client xlator
>> > 4 mount the volume by customized volume file above
>> > /usr/sbin/glusterfs --volfile=<volume file> --volfile-id=volume
>> > mountpoint
>> > Then the glusterfs client will use local port which is larger than
>> > 1024 and the port conflicts issue can be resolved.
>> >
>> > 2013/3/12, 符永涛 <yongtaofu at gmail.com>:
>> >> dear gluster experts, any suggestions? Thank you very much.
>> >>
>> >> 2013/3/11, 符永涛 <yongtaofu at gmail.com>:
>> >>> Dear gluster experts,
>> >>> I recently run into an problem related to glusterfs client
>> >>> process
>> >>> occupy rsync port 873. Since there're serveral volumes in our
>> >>> client
>> >>> machines the port conflicts may occur. Is ther any easy way to
>> >>> solve
>> >>> this problem? Thank you very much.
>> >>>
>> >>> --
>> >>> 符永涛
>> >>>
>> >>
>> >>
>> >> --
>> >> 符永涛
>> >>
>> >
>> >
>> > --
>> > 符永涛
>> >
>>
>>
>> --
>> 符永涛
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>


-- 
符永涛