You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/06/06 23:28:30 UTC
[jira] Resolved: (HADOOP-279) running without the hadoop script
causes warnings about log4j not being configured correctly
[ http://issues.apache.org/jira/browse/HADOOP-279?page=all ]
Doug Cutting resolved HADOOP-279:
---------------------------------
Fix Version: 0.3.2
(was: 0.3.1)
Resolution: Fixed
I just committed this. Thanks, Owen.
> 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.2
> 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