Bug 763703 (GLUSTER-1971) - diagnostics.client-log-level doesn't work when set to set to TRACE
Summary: diagnostics.client-log-level doesn't work when set to set to TRACE
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1971
Product: GlusterFS
Classification: Community
Component: logging
Version: 3.1.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Pavan Vilas Sondur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-18 22:00 UTC by Harshavardhana
Modified: 2015-03-23 01:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: DNR
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.