[
https://issues.apache.org/jira/browse/HDFS-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757391#action_12757391
]
Tsz Wo (Nicholas), SZE commented on HDFS-506:
---------------------------------------------
> Why are you so against committing this patch when there is already OS
> specific code in the rest of the system? ...
Because we have to maintain such OS specific codes forever. Once the codes
have got in, it is hardly to remove them because removing them becomes an
incompatible change.
I do not know much details on LinuxTaskController and the use of fork(), the
problems you mentioned previously. But if they are done by mistakes, they are
not excuses to make more mistakes.
> 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.
