[LOGCXX-26] Default initialization is broken

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.9.7
• Fix Version/s: 0.10.0
• Component/s: Configurator
• Environment: Linux (SuSE)
• Assignee: Curt Arnold
• Reporter: Martin Landers
• Created: 20/Oct/04 12:56
• Updated: 22/Oct/04 04:55
• Resolved: 22/Oct/04 04:55

Description

log4cxx's current default initializion is broken on Linux (and possibly a large number of other systems), because log4cxx sticks a little too close to log4j's ideas:

The current mechanism is using environment variables containing
a dot for its configuration. As stated in the short introduction:
"The preferred way to specify the default initialization file is through the log4j.configuration environment variable."

The problem is, that it's impossible to create environment variables containing a dot on Linux systems, meaning you're unable to use the preferred way of default initialization on Linux...

I've created a small, backward-compatible patch, that goes on
to check a few additional environment variables (LOG4J_CONFIGURATION
and LOG4CXX_CONFIGURATION) if log4j.configuration is unset allowing
UNIX-types to use these instead of the ones with the dot. The patch
also updates the documentation in the short introduction.