[
https://issues.apache.org/jira/browse/HADOOP-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760436#action_12760436
]
Owen O'Malley commented on HADOOP-6272:
---------------------------------------
If someone has free cycles, I agree that fixing HADOOP-4998 would be great.
In the mean time, I don't want to hard code paths for each particular operating
system. If we take a patch for Solaris, it doesn't make sense to reject patches
that add the path for the whoami command under BSD, etc.
In the short term, I'd suggest documenting the soft link fix in the hadoop/bin
directory.
In the medium (0.22) term, we'll have Kerberos and Unix login via Jaas and
groups done server side via HADOOP-4656.
> 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.
