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

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 without having to restart glusterd? Is there anyway to restart glusterd without killing it

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

Would also be nice if auth.allow could take DNS entries similar to the way that /etc/exports for NFS can read these types of entries, e.g. *.blah.foo.edu On Tue, Jan 15, 2013 at 5:59 PM, Sabuj Pattanayek sab...@gmail.com wrote: Hi, Anyone know if the 1024 char limit for auth.allow still exists

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

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