https://sourceforge.net/p/log4cpp/bugs/99/2006-01-12T02:29:47ZRecent changes to 99: a problem on reloading configure file2006-01-12T02:29:47Z2006-01-12T02:29:47ZWu Huajiehttps://sourceforge.net/u/wuhuajie/https://sourceforge.nete0815588d7bedd88ba1f4b4f0fa561712341d538

<div class="markdown_content"><p>I have two configure files.</p> <p>file1: mycim.props<br /> ....<br /> log4cpp.category.runLog=DEBUG,runFileAppender,runConso<br /> leAppender<br /> ....<br /> log4cpp.appender.runFileAppender.threshold=DEBUG<br /> ....<br /> log4cpp.category.runLog.CommandLgr<br /> log4cpp.category.runLog.CommandLgr.IncludeLgr=WARN</p> <p>file 2: mycim.props1<br /> ....<br /> log4cpp.category.runLog=DEBUG,runFileAppender,runConso<br /> leAppender<br /> ....<br /> log4cpp.appender.runFileAppender.threshold=DEBUG<br /> ....<br /> log4cpp.category.runLog.CommandLgr<br /> log4cpp.category.runLog.CommandLgr.IncludeLgr.</p> <p>file 1 is my current configure file, <br /> so "log4cpp.category.runLog.CommandLgr.IncludeLgr" <br /> is at the log level WARN and above.</p> <p>Then I change my configure file to file2 dynamically.<br /> it is expected <br /> that "log4cpp.category.runLog.CommandLgr.IncludeLgr" <br /> is at the level same as runlog.</p> <p>But it acts that IncludeLgr is at the log level WARN <br /> and above actually. Stay unchanged. </p> <p>Reason is that library log4cpp will skip the lines <br /> without '=' in the configure file. <br /> so the log level IncludeLgr will not change from WARN <br /> to NOTSET as expected.</p></div>