Bug 763703 (GLUSTER-1971)

Summary:	diagnostics.client-log-level doesn't work when set to set to TRACE
Product:	[Community] GlusterFS	Reporter:	Harshavardhana <fharshav>
Component:	logging	Assignee:	Pavan Vilas Sondur <pavan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	3.1.0	CC:	cww, gluster-bugs, vijay
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	DNR	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Harshavardhana 2010-10-18 22:00:08 UTC

Starting a volume and setting the client-log-level to TRACE doesn't work. 

We have to manually start NFS server to with "-L TRACE" to make it work. 

Reproducible all the time with 3.1 GA release. 

All i see is the log file has a different time stamp altogether.