[ http://issues.apache.org/jira/browse/NUTCH-318?page=comments#action_12423555 ] Andrzej Bialecki commented on NUTCH-318: -----------------------------------------
Ok, go ahead, it makes sense in this case. However, there are many places where displaying INFO messages on the console also makes sense, again - especially in the local mode. Otherwise you have to start a new console, and do a 'tail -f logs/hadoop.log', which seems like an awkward and complicated way to see if your command makes any progress or is stuck. So, I would vote for adding stdout for now. I know it produces messy output, and a lot of it - perhaps we could exclude some stuff from stdout, like plugin repository loading, config parsing etc. But my feeling is that at least some info should be displayed on the console. > log4j not proper configured, readdb doesnt give any information > --------------------------------------------------------------- > > Key: NUTCH-318 > URL: http://issues.apache.org/jira/browse/NUTCH-318 > Project: Nutch > Issue Type: Bug > Affects Versions: 0.8-dev > Reporter: Stefan Groschupf > Priority: Critical > Fix For: 0.9-dev > > > In the latest .8 sources the readdb command doesn't dump any information > anymore. > This is realeated to the miss configured log4j.properties file. > changing: > log4j.rootLogger=INFO,DRFA > to: > log4j.rootLogger=INFO,DRFA,stdout > dumps the information to the console, but not in a nice way. > What makes me wonder is that these information should be also in the log > file, but the arn't, so there are may be even here problems. > Also what is the different between hadoop-XXX-jobtracker-XXX.out and > hadoop-XXX-jobtracker-XXX.log ?? Shouldn't there just one of them? -- 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
