[Gluster-users] auth.allow behavior?
harry.mangalam at uci.edu
Wed Nov 2 00:21:53 UTC 2011
On Tuesday 01 November 2011 16:53:56 Joe Landman wrote:
On 11/01/2011 06:09 PM, Harry Mangalam wrote:
> > What else sets the authentication / permission correctly?
> gluster volume set g6 auth.allow 192.168.*,128.*
That doesn't cause an error and it does cause itself to be inserted
into the volume info:
root at pbs3:~
561 $ gluster volume info
Volume Name: g6
Number of Bricks: 6
AND after volume stop/start (but NOT before), it DOES come back for
the clients that could originally mount it.
AND IT NOW WORKS FOR THE OTHER clients as well.
- auth.allow supports multiple addresses IF they're separated with ','
but not with spaces (not documented, more silent failures)
- volumes have to be stopped and restarted to propagate these changes
(another silent .. if not failure, the absence of a warning that
indicates that on auth.allow (and all other option?) changes, you have
to restart the volume to activate it.
This does not seem to be documented in the Gluster_FS_3.2_Admin_Guide
that I have. I guess I should be going thru the wiki on this...
Joe gets an ebeer (12pack!) :)
Harry Mangalam - Research Computing, OIT, Rm 225 MSTB, UC Irvine
[ZOT 2225] / 92697 Google Voice Multiplexer: (949) 478-4487
MSTB Lat/Long: (33.642025,-117.844414) (paste into Google Maps)
This signature has been OCCUPIED!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users