#99 a problem on reloading configure file

[Wu Huajie]

I have two configure files.

file1: mycim.props
....
log4cpp.category.runLog=DEBUG,runFileAppender,runConso
leAppender
....
log4cpp.appender.runFileAppender.threshold=DEBUG
....
log4cpp.category.runLog.CommandLgr
log4cpp.category.runLog.CommandLgr.IncludeLgr=WARN

file 2: mycim.props1
....
log4cpp.category.runLog=DEBUG,runFileAppender,runConso
leAppender
....
log4cpp.appender.runFileAppender.threshold=DEBUG
....
log4cpp.category.runLog.CommandLgr
log4cpp.category.runLog.CommandLgr.IncludeLgr.

file 1 is my current configure file,
so "log4cpp.category.runLog.CommandLgr.IncludeLgr"
is at the log level WARN and above.

Then I change my configure file to file2 dynamically.
it is expected
that "log4cpp.category.runLog.CommandLgr.IncludeLgr"
is at the level same as runlog.

But it acts that IncludeLgr is at the log level WARN
and above actually. Stay unchanged.

Reason is that library log4cpp will skip the lines
without '=' in the configure file.
so the log level IncludeLgr will not change from WARN
to NOTSET as expected.