<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
I adjusted this part using the bricks hostname instead localhost, as you can see here:<br>
<br>
snprintf (cmd_str, 8192,<br>
"%s/sbin/glusterfsd --xlator-option %s-server.listen-port=%d "<br>
"-s %s --volfile-id %s -p %s --brick-name %s "<br>
"--brick-port %d -l %s", GFS_PREFIX, volinfo->volname,<br>
port, brickinfo->hostname, volfile, pidfile, brickinfo->path, port,<br>
brickinfo->logfile);<br>
<br></blockquote><div> </div><div>This change is fine.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
I think the solution is okay, but better would be if glusterd considers the optionally --remote-host= parameter instead<br>
the bricks host. Maybe anybody can tell me how I have to adjust it.<br>
<br></blockquote><div><br></div><div>To start 'glusterfsd' bind()'d to particular IP, you need to edit glusterd-volgen.c and add an option to 'protocol/server' volume saying 'option bind-address <IP>'</div>
<div><br></div><div>That should make glusterfsd listen on particular IP instead of binding to 0.0.0.0</div><div></div></div><br><div>Regards,</div><div>Amar</div>