Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <16110196.1149625230599.JavaMail.jira@brutus>
Date: Tue, 6 Jun 2006 20:20:30 +0000 (GMT+00:00)
From: "Owen O'Malley (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-279) running without the hadoop script
 causes warnings about log4j not being configured correctly
In-Reply-To: <7237468.1149624869823.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/HADOOP-279?page=all ]

Owen O'Malley updated HADOOP-279:
---------------------------------

    Attachment: default-hadoop-root-logger.patch

This patch sets default values for the three system properties that are used in the default property files.

hadoop.root.logger=INFO,stdout
hadoop.log.dir=.
hadoop.log.file=hadoop.log

It also includes some examples of increasing logging levels.

> running without the hadoop script causes warnings about log4j not being configured correctly
> --------------------------------------------------------------------------------------------
>
>          Key: HADOOP-279
>          URL: http://issues.apache.org/jira/browse/HADOOP-279
>      Project: Hadoop
>         Type: Improvement

>   Components: mapred
>     Versions: 0.3.1
>     Reporter: Owen O'Malley
>     Assignee: Owen O'Malley
>      Fix For: 0.3.1
>  Attachments: default-hadoop-root-logger.patch
>
> Anyone who runs hadoop programs without the bin/hadoop script will get a message about log4j not being configured correctly. The problem is that the config file uses the system property "hadoop.root.logger", which is set in the script.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira