The problem I have with CONFIG is that the applications I deployed usually set their default log level to ERROR, so enabling CONFIG would also enable WARN, which isn’t what was desired. Using a CONFIG marker eliminates this problem.
Ralph On Jan 18, 2014, at 12:30 PM, Nicholas Williams <nicho...@nicholaswilliams.net> wrote: > I explained in the email why CONFIG > INFO. Not sure I can explain it any > better. :-/ > > To repeat in case you didn't see it: > >>> My reason for putting CONFIG between INFO and WARN is simple: I ALWAYS want >>> to see config-related messages when the application starts, but I don't >>> always want to see INFO messages after it starts. And if something >>> re-configures while the application is running, I want to see that, too. >>> I've developed the habit of logging startup messages as WARNings, which I >>> don't like doing. > > Nick > > Sent from my iPhone from a Southwest jet, so please forgive brief replies and > frequent typos > >> On Jan 18, 2014, at 12:27, Gary Gregory <garydgreg...@gmail.com> wrote: >> >> My reason for putting CONFIG between INFO and WARN is simple: I ALWAYS want >> to see config-related messages when the application starts, but I don't >> always want to see INFO messages after it starts. And if something >> re-configures while the application is running, I want to see that, too. >> I've developed the habit of logging startup messages as WARNings, which I >> don't like doing. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
