<div dir="ltr">Thank you Dave. Those variables were already nil but I did find something.. Yesterday I had received an error, "stdout is closed" and so, perplexed but in need of moving forward at that time, I went ahead and put a call to #ensureOpen prior to each write to stdout and stderr.<div>
<br></div><div style>I removed that again today and, at least for a quick test, all seems to be fine again. I'm not sure why I got that error about it being closed before..</div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Tue, Apr 2, 2013 at 8:05 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Tue, Apr 02, 2013 at 07:53:06PM -0500, Chris Muller wrote:<br>
> I have an image that seems to no longer be able to write to stdout or<br>
> stderr. It most definitely was doing that at one time, but now none of the<br>
> redirection works, however I am seeing actual files called "stdout" and<br>
> "stderr" in the image directory with output from all of my running images<br>
> written on top of each other -- unreadable.<br>
><br>
> Just to make sure it wasn't something in my OS, I tried another image and<br>
> writing to stdout works fine.<br>
><br>
> I'd like to stay in this image if I can, is there some way to "reset"<br>
> things back to normal? I poked around in the related FileStream methods<br>
> but didn't see anything quick and obvious..<br>
<br>
</div></div>You can probably just nil out the Stdout Stderr Stdin class variables in<br>
FileStream, and I expect that everything will return to normal once reinitialized.<br>
<br>
And of course you can always use the old standby:<br>
<br>
OSProcess thisOSProcess stdOut<br>
OSProcess thisOSProcess stdErr<br>
OSProcess thisOSProcess stdIn<br>
<br>
Dave<br>
<br>
<br>
</blockquote></div><br></div>