Re: Disabling non-syslog logging

[Amar Tumballi <amar@xxxxxxxxxxx>]

>

> can you try 'gluster volume set <VOLNAME> client-log-level
NONE' ?
>

Thanks for the suggestion;

 Running this (glusterfs v3.2.6) works (logs a succeed
message) but the bricks continue to accrue client
connection notices. There is also still the .cmd-history
log amongst other files.

 Note that the objective here is no log files at all; i.e. at
the moment if the directory /var/log/glusterfs is not
created gluster fails to run.  This was not the behaviour
under the older architecture, when "-l /dev/null" was
specified ..

Oops,

then try

bash# gluster volume set <VOLNAME> brick-log-level NONE
 

and see if there are no logs now...