hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Moved: (HADOOP-6272) Incorrect UserName at Solaris because it has no "whoami" command by default
Date Fri, 18 Sep 2009 21:34:17 GMT

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

Todd Lipcon moved HDFS-506 to HADOOP-6272:
------------------------------------------

          Component/s:     (was: documentation)
                       util
                       security
    Affects Version/s:     (was: 0.20.1)
                       0.21.0
                       0.20.1
                  Key: HADOOP-6272  (was: HDFS-506)
              Project: Hadoop Common  (was: Hadoop HDFS)

> Incorrect UserName at Solaris because it has no "whoami" command by default
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-6272
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6272
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security, util
>    Affects Versions: 0.20.1, 0.21.0
>         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