[
https://issues.apache.org/jira/browse/MESOS-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617869#comment-14617869
]
haosdent edited comment on MESOS-2199 at 7/8/15 2:41 AM:
---------------------------------------------------------
{quote}
I think it's flawed to require global read access for the build directory...
{quote}
Hi, [~idownes].If nobody could not read /home/idownes/build, he also could not
read /home/idownes/build/src/.libs/lt-mesos-executor and execute.
So the contradictory place appears:
1. if we want nobody could execute
/home/idownes/build/src/.libs/lt-mesos-executor, he should have "r-x"
permissions in these directories:
{code}
/home
/home/idownes
/home/idownes/build
/home/idownes/build/src
/home/idownes/build/src/.libs
{code}
2. if we don't want nobody access /home/idownes/ , he also could not execute
/home/idownes/build/src/.libs/lt-mesos-executor because lt-mesos-executor
belongs to /home/idownes/
More details is
[here|http://unix.stackexchange.com/questions/13858/do-the-parent-directorys-permissions-matter-when-accessing-a-subdirectory].
And need "chmod o+x /home/idownes"
was (Author: [email protected]):
{quote}
I think it's flawed to require global read access for the build directory...
{quote}
Hi, [~idownes].If nobody could not read /home/idownes/build, he also could not
read /home/idownes/build/src/.libs/lt-mesos-executor and execute.
So the contradictory place appears:
1. if we want nobody could execute
/home/idownes/build/src/.libs/lt-mesos-executor, he should have "r-x"
permissions in these directories:
{code}
/home
/home/idownes
/home/idownes/build
/home/idownes/build/src
/home/idownes/build/src/.libs
{code}
2. if we don't want nobody access /home/idownes/ , he also could not execute
/home/idownes/build/src/.libs/lt-mesos-executor because lt-mesos-executor
belongs to /home/idownes/
More details is here. And need "chmod o+x /home/idownes"
> Failing test: SlaveTest.ROOT_RunTaskWithCommandInfoWithUser
> -----------------------------------------------------------
>
> Key: MESOS-2199
> URL: https://issues.apache.org/jira/browse/MESOS-2199
> Project: Mesos
> Issue Type: Bug
> Components: test
> Reporter: Ian Downes
> Assignee: haosdent
> Labels: mesosphere
>
> Appears that running the executor as {{nobody}} is not supported.
> [~nnielsen] can you take a look?
> Executor log:
> {noformat}
> [root@hostname build]# cat
> /tmp/SlaveTest_ROOT_RunTaskWithCommandInfoWithUser_cxF1dY/slaves/20141219-005206-2081170186-60487-11862-S0/frameworks/20141219-005206-2081170186-60
> 487-11862-0000/executors/1/runs/latest/std*
> sh: /home/idownes/workspace/mesos/build/src/mesos-executor: Permission denied
> {noformat}
> Test output:
> {noformat}
> [==========] Running 1 test from 1 test case.
> [----------] Global test environment set-up.
> [----------] 1 test from SlaveTest
> [ RUN ] SlaveTest.ROOT_RunTaskWithCommandInfoWithUser
> ../../src/tests/slave_tests.cpp:680: Failure
> Value of: statusRunning.get().state()
> Actual: TASK_FAILED
> Expected: TASK_RUNNING
> ../../src/tests/slave_tests.cpp:682: Failure
> Failed to wait 10secs for statusFinished
> ../../src/tests/slave_tests.cpp:673: Failure
> Actual function call count doesn't match EXPECT_CALL(sched,
> statusUpdate(&driver, _))...
> Expected: to be called twice
> Actual: called once - unsatisfied and active
> [ FAILED ] SlaveTest.ROOT_RunTaskWithCommandInfoWithUser (10641 ms)
> [----------] 1 test from SlaveTest (10641 ms total)
> [----------] Global test environment tear-down
> [==========] 1 test from 1 test case ran. (10658 ms total)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
