> Suppose Logger A is set to WARN. > Suppose Logger A.B.C is set to DEBUG. > Now suppose the entry in the config file setting A.B.C to > DEBUG is removed.
It is removed from the file and the file is re-read to set the current configuration, right? > Q: Does A.B.C inherit from A at this point, yielding a level > of WARN, or > does the level of A.B.C continue at DEBUG until explicitly > set back to WARN? No, the level setting for A.B.C is not changed. At least with the DOMConfigurator (I assume the same is true for PropertyConfigurator), the level settings for loggers is not reset before the file is processed, and the setting is only changed if the logger is explicitly set in the config file. If you want that behavior, the only way to get it at this point is to call LoggerRepository.resetConfiguration() before re-reading the config file. We have discussed adding a "reset" attribute to xml files (similar to the "debug" attribute) that would do this action for you, allowing a reset to occur if you are using a watchdog to watch a config file. Of course, the real trick is to reset the configuration but not lose any important logger messages in the time between the reset and the time the config file is re-read. I have code that accomplishes this for the DOMConfigurator, and I hope to review and add for v1.3. It requires some modifications to the DOMConfigurator code. hth, -Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
