><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> can you try 'gluster volume set <VOLNAME> client-log-level<br>
NONE' ?<br>
><br>
<br>
</div>Thanks for the suggestion;<br>
<br>
Running this (glusterfs v3.2.6) works (logs a succeed<br>
message) but the bricks continue to accrue client<br>
connection notices. There is also still the .cmd-history<br>
log amongst other files.<br>
<br>
Note that the objective here is no log files at all; i.e. at<br>
the moment if the directory /var/log/glusterfs is not<br>
created gluster fails to run. This was not the behaviour<br>
under the older architecture, when "-l /dev/null" was<br>
specified ..<br>
<div class="im HOEnZb"><br><br></div></blockquote><div>Oops,<br><br>then try<br><br>bash# gluster volume set <VOLNAME> brick-log-level NONE <br> <br></div></div>and see if there are no logs now...<br><br>