You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2016/04/04 18:18:25 UTC
[jira] [Updated] (MESOS-4882) Enabled mesos-execute treat command
as executable value and arguments.
[ https://issues.apache.org/jira/browse/MESOS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jie Yu updated MESOS-4882:
--------------------------
Shepherd: Alexander Rukletsov (was: Jie Yu)
> Enabled mesos-execute treat command as executable value and arguments.
> ----------------------------------------------------------------------
>
> Key: MESOS-4882
> URL: https://issues.apache.org/jira/browse/MESOS-4882
> Project: Mesos
> Issue Type: Bug
> Reporter: Guangya Liu
> Assignee: Guangya Liu
>
> The commandInfo support two kind of command:
> {code}
> // There are two ways to specify the command:
> // 1) If 'shell == true', the command will be launched via shell
> // (i.e., /bin/sh -c 'value'). The 'value' specified will be
> // treated as the shell command. The 'arguments' will be ignored.
> // 2) If 'shell == false', the command will be launched by passing
> // arguments to an executable. The 'value' specified will be
> // treated as the filename of the executable. The 'arguments'
> // will be treated as the arguments to the executable. This is
> // similar to how POSIX exec families launch processes (i.e.,
> // execlp(value, arguments(0), arguments(1), ...)).
> {code}
> The mesos-execute cannot handle 2) now, enabling 2) can help some unit test with isolator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)