[Gluster-devel] name of server provided client config?
Amar S. Tumballi
amar at zresearch.com
Thu Jul 10 15:50:15 UTC 2008
No worries, it looks for client.vol.<ip-addr> first and looks for the
regular file whatever is given as the option. So, you need not worry about
the <ip-addr> part, that was mostly used when spec file changes per client
(like NUFA setup), etc.
2008/7/10 John Marshall <John.Marshall at ec.gc.ca>:
> Instead of copying the gluster client vol file to all my clients, I am
> pulling it from the server. But when I do this, the server is looking
> for a file like glusterfs-client.vol.<ipaddr> . Is this expected? Does
> it mean that I need to do something like put symlinks to the
> glusterfs-client.vol file for all clients ipaddrs?
> My glusterfs-server.vol file is below.
> ### Export volume "brick" with the contents of "/home/export" directory.
> volume cava_test0
> type storage/posix # POSIX FS translator
> option directory /mnt/cava_test0 # Export this directory
> ### Add network serving capability to above brick.
> volume server
> type protocol/server
> option transport-type tcp/server # For TCP/IP transport
> option client-volume-filename /etc/glusterfs/glusterfs-client.vol
> subvolumes cava_test0
> option auth.ip.cava_test0.allow * # Allow access to volume
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
[bulde on #gluster/irc.gnu.org]
http://www.zresearch.com - Commoditizing Super Storage!
More information about the Gluster-devel