Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 20 Nov 2012 21:35:00 +0000 (UTC)
From: "Matt Foley (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <2013976036.9246.1353447301044.JavaMail.jiratomcat@arcas>
In-Reply-To: <1685731167.56388.1351784232882.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HDFS-4134) hadoop namenode & datanode entry
 points should return negative exit code on bad arguments
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Matt Foley updated HDFS-4134:
-----------------------------

    Fix Version/s:     (was: 1.2.0)
    
> 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
>             Fix For: 1.1.1
>
>         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