<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Wed, Jun 12, 2013 at 2:47 AM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im">On Tue, Jun 11, 2013 at 10:34:47PM -0700, Sean P. DeNigris wrote:<br>
> When using PipeableOSProcess as a shell, how can I get feedback on the status<br>
> of the individual commands?<br></div>[snip]<br><div>
PipeableOSProcess is designed to be part of CommandShell, so when you use it<br>
directly (rather than using a CommandShell), you need to take care of a few<br>
details. The important things are to set the output pipe for nonblocking reads<br>
(otherwise you will hang up your VM on a read), and to close pipes when you<br>
are done using them (otherwise you will "leak" file handles over time).<br>
<br>
Dave<br>
<div class=""><div class="h5"><br></div></div></div></blockquote></div><br clear="all">Could the example you gave be implemented using CommandShell? In what
situations would I want to use PipeableOSProcess instead of
CommandShell?<br>-- <br>Gary Dunn<br>Open Slate Project<br><a href="http://openslate.org/" target="_blank">http://openslate.org/</a>
</div></div>