You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2012/11/08 22:38:12 UTC
[jira] [Updated] (HDFS-4134) hadoop namenode & datanode entry
points should return negative exit code on bad arguments
[ https://issues.apache.org/jira/browse/HDFS-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Srinivas updated HDFS-4134:
----------------------------------
Summary: hadoop namenode & datanode entry points should return negative exit code on bad arguments (was: hadoop namenode & datanode entry points should return -1 exit code on bad arguments)
> hadoop namenode & datanode entry points should return negative exit code on bad arguments
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-4134
> URL: https://issues.apache.org/jira/browse/HDFS-4134
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 1.0.4
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: HDFS-4134.patch
>
>
> When you go {{hadoop namenode start}} (or some other bad argument to the namenode), a usage message is generated -but the script returns 0.
> This stops it being a robust command to invoke from other scripts -and is inconsistent with the JT & TT entry points, that do return -1 on a usage message
--
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