[Gluster-devel] GlusterFS 1.3.0-pre2.3: glusterfs command option: --server

Gerry Reno greno at verizon.net
Thu Apr 5 23:02:12 UTC 2007

Anand Babu Periasamy wrote:
> Gerry Reno writes:
>> Is this a bug with the client command option: --server ? Or is
>> something else expected as an argument?
>> glusterfs -l /var/log/glusterfs.log -L DEBUG --spec-file
>> /usr/local/etc/glusterfs/test-client.vol --server=
>> --port=6996 /mnt/glusterfs0/ #THIS COMMAND DOES NOT WORK
>> glusterfs -l /var/log/glusterfs.log -L DEBUG --spec-file
>> /usr/local/etc/glusterfs/test-client.vol --port=6996
>> /mnt/glusterfs0/ #THIS COMMAND DOES WORK (run from
> Hi Gerry,
> --server option overrides --spec-file to fetch the spec file from the
> server instead. Also --port requires --server.
> I fixed it to behave as you expected. Now glusterfs client will error
> out with an appropriate message for the following cases:
> * if you combine --spec-file and --server
> * if you pass --port and not --server
> Thanks for reporting. Fix is in GNU TLA archive.
I'm not sure I understand this. If --server is to override --spec-file,
then how does it know where to find the specfile without the --spec-file
argument? I mean I could put the specfile anywhere.
My original concern was that the combination of --server and --port did
not work at least not if the specified server was the same as the server
from which you ran the command.
In random fiddling with the arguments I was able to find that when I
left out the --server then the command would work which seemed a little odd.


More information about the Gluster-devel mailing list