You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2013/01/12 21:22:13 UTC

[jira] [Updated] (NUTCH-342) Nutch commands log to nutch/logs/hadoop.logs by default

     [ https://issues.apache.org/jira/browse/NUTCH-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lewis John McGibbney updated NUTCH-342:
---------------------------------------

       Patch Info: Patch Available
    Fix Version/s: 2.2
                   1.7
    
> Nutch commands log to nutch/logs/hadoop.logs by default
> -------------------------------------------------------
>
>                 Key: NUTCH-342
>                 URL: https://issues.apache.org/jira/browse/NUTCH-342
>             Project: Nutch
>          Issue Type: Bug
>    Affects Versions: 0.8
>            Reporter: Chris Schneider
>            Priority: Minor
>             Fix For: 1.7, 2.2
>
>         Attachments: NUTCH-342.patch
>
>
> If (by default) Nutch commands are going to send their output to a file named "hadoop.log", then it seems like the default location for this file should be the same location where Hadoop is putting its hadoop.log file (i.e., $HADOOP_LOG_DIR). Currently, if I set HADOOP_LOG_DIR to a special location (via hadoop-env.sh), this has no effect on where Nutch commands send their output.
> Some would probably suggest that I could just set NUTCH_LOG_DIR to $HADOOP_LOG_DIR myself. I still think that it should be defaulted this way in the nutch script. However, I'm unaware of an elegant way to modify such Nutch environment variables anyway. The hadoop-env.sh file provides a convenient place to modify Hadoop environment variables, but doing the same for Nutch environment variables presumably requires you to modify .bash_profile or a similar user script file (which is the way I used to accomplish this kind of thing with Nutch 0.7).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira