[Gluster-users] 1024 char limit for auth.allow and automatically re-reading auth.allow without having to restart glusterd?

[James]

On Tue, 2013-01-15 at 17:59 -0600, Sabuj Pattanayek wrote:
> Hi,
> 
> Anyone know if the 1024 char limit for auth.allow still exists in the
> latest production version (seems to be there in 3.2.5). Also anyone
> know if the new versions check if auth.allow has been updated
Do you mean do you want to know what the value of 'auth.allow' is ?
I have code in my puppet-gluster module that checks this. Maybe it's
what you're looking for. If so, then I hope this helps.

https://github.com/purpleidea/puppet-gluster
more specifically:
https://github.com/purpleidea/puppet-gluster/blob/master/manifests/volume/property.pp
Cheers,
James

>  without
> having to restart glusterd? Is there anyway to restart glusterd
> without killing it and restarting the process, is kill -1 (HUP)
> possible with it (also with the version i'm running?)
> 
> Thanks,
> Sabuj
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130115/73915fb7/attachment.sig>