[
https://issues.apache.org/jira/browse/MESOS-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697739#comment-14697739
]
Marco Massenzio commented on MESOS-3035:
----------------------------------------
Hey [~pbrett] - I was looking at your
[r/37045|https://reviews.apache.org/r/37045] and thought "great minds think
alike" :)
Can you please take a quick view at what I've done in the review posted (above)
and let me know whether the refactoring in {{Subprocess}} would help your use
case (and, also, if you can spot where I went wrong? there is something, when
the thing times out, I believe, that causes a SIGABRT - but still the tests,
weirdly, pass).
Thanks!
> As a Developer I would like a standard way to run a Subprocess in libprocess
> ----------------------------------------------------------------------------
>
> Key: MESOS-3035
> URL: https://issues.apache.org/jira/browse/MESOS-3035
> Project: Mesos
> Issue Type: Story
> Components: libprocess
> Reporter: Marco Massenzio
> Assignee: Marco Massenzio
>
> As part of MESOS-2830 and MESOS-2902 I have been researching the ability to
> run a {{Subprocess}} and capture the {{stdout / stderr}} along with the exit
> status code.
> {{process::subprocess()}} offers much of the functionality, but in a way that
> still requires a lot of handiwork on the developer's part; we would like to
> further abstract away the ability to just pass a string, an optional set of
> command-line arguments and then collect the output of the command (bonus:
> without blocking).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
