hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-506) Incorrect UserName at Solaris because it has no "whoami" command by default
Date Thu, 17 Sep 2009 21:13:57 GMT

    [ https://issues.apache.org/jira/browse/HDFS-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756792#action_12756792
] 

Allen Wittenauer commented on HDFS-506:
---------------------------------------

>From where I sit, this is what I see happening:

a) We are afraid of writing JNI code, even tho the JNI code that needs to be written should
be highly portable since it is all POSIX stuff. [HADOOP-4998]

b) We are not willing to write special case OS code for determining what the user is and instead
dependent upon user's hacking up their path in likely incompatible ways. [what this and other
bugs are about]

c) We are willing to write special case OS code for dealing with memory management for the
MapReduce framework. [See LinuxTaskController]

So we now have (essentially) two patches that may make the situation better.  Would someone
explain to me why either HADOOP-4603 or this one isn't getting committed?  

> Incorrect UserName at Solaris because it has no "whoami" command by default
> ---------------------------------------------------------------------------
>
>                 Key: HDFS-506
>                 URL: https://issues.apache.org/jira/browse/HDFS-506
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 0.20.1
>         Environment: OS: SunOS 5.10
>            Reporter: Urko Benito
>         Attachments: PermissionChecker.java.diff, Shell.java.diff, test-hadoop-security.tar.gz,
UnixUserGroupInformation.java.diff
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Solaris enviroment has no __whoami__ command, so the __getUnixUserName()__ at UnixUserGroupInformation
class fails because it's calling to Shell.USER_NAME_COMMAND which is defines as "whoami".
> So it launched an Exception and set the default "DrWho" username ignoring all the FileSystem
permissions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message