REVIEW: http://review.gluster.org/6726 (gfapi: Set log level to GF_LOG_NONE after closing log file in glfs_fini) posted (#1) for review on master by poornima g (pgurusid)

REVIEW: http://review.gluster.org/6726 (gfapi: Set log level to GF_LOG_NONE after closing log file in glfs_fini) posted (#2) for review on master by poornima g (pgurusid)

REVIEW: http://review.gluster.org/6726 (gfapi: Set log level to GF_LOG_NONE after closing log file in glfs_fini) posted (#3) for review on master by Poornima G (pgurusid)

COMMIT: http://review.gluster.org/6726 committed in master by Anand Avati (avati) 
------
commit 8eb83e6d9a91c813275f1cbc8e0dc5423fb1ccc0
Author: Poornima <pgurusid>
Date:   Fri Jan 17 02:45:56 2014 +0000

    gfapi: Set log level to GF_LOG_NONE after closing log file in glfs_fini
    
    Currently any logs that are logged after calling glfs_fini will
    appear on stderr. Ideally to the end of the glfs_fini all the
    operations will be complete and there should be no further logging.
    But it appears that the client translator is still up and prints
    some log messages even after calling glfs_fini.
    
    In this patch the log level is set to GF_LOG_NONE once the log file
    is closed. This fix is not required if wait for "CHILD_DOWN" event
    is implemented in glfs_fini.
    
    Change-Id: Idde80e9a89f3a5264d02b7e6fc2a84d67550b20a
    BUG: 1054696
    Signed-off-by: Poornima <pgurusid>
    Reviewed-on: http://review.gluster.org/6726
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Anand Avati <avati>

Poornima, 

Let this BZ flow through its normal lifecycle.
I am greatly interested in understanding and verify this bug.

So, I am planning to move this bug to ON_QA and verify it with the fix.
Does that cause any concern/harm ?

No, not at all, the same patch was verified as a part of BZ 1046259, hence closed the bug.