Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 4 Aug 2015 13:57:05 +0000 (UTC)
From: "Chang Li (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12851204.1438634338000.366988.1438696625071@Atlassian.JIRA>
In-Reply-To: <JIRA.12851204.1438634338000@Atlassian.JIRA>
References: <JIRA.12851204.1438634338000@Atlassian.JIRA>
 <JIRA.12851204.1438634338882@arcas>
Subject: [jira] [Commented] (HADOOP-12296) when setnetgrent returns 0 in
 linux, exception should be thrown
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-12296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653674#comment-14653674 ] 

Chang Li commented on HADOOP-12296:
-----------------------------------

[~aw] thanks for providing opinion. But I still think it's reasonable to thrown an exception because when setnetgrent returns 0 in linux it's not saying the netgroup is empty, but it's actually saying the passed netgroup name is invalid (misconfigured) or if any error occurred.  

> when setnetgrent returns 0 in linux, exception should be thrown
> ---------------------------------------------------------------
>
>                 Key: HADOOP-12296
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12296
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: HADOOP-12296.2.patch, HADOOP-12296.patch
>
>
> In linux, setnetgrent returns 0 in linux when something wrong is happen, such as out of memory, unknown group, unavailable service, etc. So errorMessage should be set and exception should be thrown


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)