>> Also, since I am asking questions, how do you turn off logging completely >> for a category? Would you just set the priority to FATAL_ERROR? > >That would still catch fatal errors. The best way to do it would be to attach >a NullOutputLogTarget
I glanced at the code and I was wondering if are you going to lose efficiency by simply setting a null log target? So, for instance, if DEBUG is enabled, but the log target is the bit bucket, I have already had the JVM go through the expensive string operations building a message to log only to have it thrown away. Would it make more sense to have something like Priority.NONE so that overhead is avoided? As I mentioned before, I want to be able to set different priorities at runtime for logging and then be able to turn it off without restarting the app. It seems like it will always be on in some fashion even though I am not logging anywhere. Is that the case or is there something else that I am missing? Thanks for your help. Tony -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
