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

[Sabuj Pattanayek]

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 <sabujp at gmail.com> 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 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