[
https://issues.apache.org/jira/browse/MESOS-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343060#comment-15343060
]
Hansel Chung commented on MESOS-5633:
-------------------------------------
Normally, login/sudo will call getpwuid(getuid()), and get $HOME, $SHELL, $USER
as well as the uid and gid.
If one of them gets null, I would think the correct thing to do would be to
unset the variable.
The exception would be $HOME, which if null, would make sense to default to
$MESOS_SANDBOX.
This would help emulate the behavior if one were to start up mesos as a user
instead of root, which I would prefer. I've been using $HOME/executorDir as the
deployment location for some executors where their runtime might be on the same
order or even less than the amount of time it takes to transport the executor,
shared libraries, and config.
I don't know about other projects but mine reads from a variety of places
including the user's home dir, but writes only happen to $MESOS_DIRECTORY.
> User related shell environment is not set correctly in tasks
> ------------------------------------------------------------
>
> Key: MESOS-5633
> URL: https://issues.apache.org/jira/browse/MESOS-5633
> Project: Mesos
> Issue Type: Bug
> Reporter: haosdent
>
> If user specify the user field in {{FrameworkInfo}} or {{Task}}, both
> {{setuid}} and {{setgroups}} are set correctly. However, some user related
> shell variables, e.g., {{HOME}}, {{USER}} are still use root.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
