From: Christophe Broult <maestroiut-ruby@...>
Date: 2005-10-14T16:42:52+09:00
Subject: log4r and log4j root logger differing behavior

Hi All,

I am wondering if anyone who has used log4r and log4j has noticed
their root logger differing behaviors.

As stated in the log4r documentation:

  RootLogger Does Nothing

  RootLogger itself behaves as if its level were permanently set 
  to OFF, thus making it a sort of null object. 

When using log4j that is not the case and it is quite useful to
leverage the logger inheritance from the root logger where, for
example, one can specify the default Outputters on the root logger
and then adjust the logging level on the children.

Does anyone have a suggestion to get a behavior similar to log4j root
logger?

Christophe