Re: [Qemu-devel] [PATCH v3] block/gluster: add support to choose libgfapi logfile

2016-07-22 Thread Prasanna Kalever
On Fri, Jul 22, 2016 at 7:37 PM, Eric Blake wrote: > On 07/22/2016 06:01 AM, Prasanna Kumar Kalever wrote: >> currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded >> in a call to glfs logging api, in case if debug level is chosen to >> DEBUG/TRACE > > s/api, in case if/ap

Re: [Qemu-devel] [PATCH v3] block/gluster: add support to choose libgfapi logfile

2016-07-22 Thread Eric Blake
On 07/22/2016 06:01 AM, Prasanna Kumar Kalever wrote: > currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded > in a call to glfs logging api, in case if debug level is chosen to DEBUG/TRACE s/api, in case if/api. When the/ s/TRACE/TRACE,/ > gfapi logs will be huge and fil

[Qemu-devel] [PATCH v3] block/gluster: add support to choose libgfapi logfile

2016-07-22 Thread Prasanna Kumar Kalever
currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded in a call to glfs logging api, in case if debug level is chosen to DEBUG/TRACE gfapi logs will be huge and fill/overflow the console view. this patch provides a commandline option to mention log file path which helps in