Emmanuel Dreyfus <manu@xxxxxxxxxx> wrote: > I posted an attempt to fix it here: http://review.gluster.com/8403 More thoughts on it: On glusterd startup, first attempt to connect to the socket gets ECONNREFUSED, and that works fine later once glustershd has setup its socket, things work fine. On NetBSD, when doing 'gluster volume $volume start force', glusterd gets ENOENT. That suggests glusterd's connect() races with glustershd's unlink()/bind()/connect() which is started in __socket_server_bind(). Another workaround is to avoid the special ENOENT treatment in socket_connect(), that also fixes the problem. Is that reasonable? In the meantime I will submit another changeset to test regression. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@xxxxxxxxxx _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
