That's it! If I just throw some of the fflush commands in here and there in
strategic places, I get all the output I am looking for up to those
statements. Why would this be needed sometimes and not others?
--
View this message in context:
http://www.nabble.com/Saving-all-xterm-output-to-a-file-
Jon TURNEY wrote:
>
>
> If you really want to prove this is an xterm issue (which seems unlikely
> to me
> as this really revolves about what bash is doing), you should compare the
> behaviour between running the command under an xterm and running it under
> some
> other terminal emulator (
Okay, I'm digging a little deeper, and I think that I have noticed some
things that might be helpful and I've created some files that might shed
some light.
The files below are output from what I'm running through xterm. Auto
indicates simulations in which the output was automatically teed to a f
Sorry, I'm not entirely sure I understood all that, but I wanted to give an
update. I wrote a script and ran over 250 tests over last night using this
syntax:
./run 1 Joiner default 2>&1 | tee 2_7_09_results.dat
Only one of these tests gave output. Mark, if I understand you correctly,
the "| tee
Thanks very much. The tee works well, and is particularly helpful for
debugging. Unfortunately, it seems that sometimes the program will run and
display output as it ought to, and other times it will run and no output is
visible. I've never had this problem when not trying to output to a file, so
I am trying to automate a simulation process, and part of this involves
capturing the output that is written to an xterm window when a particular
process is run. I thought that I had this figured out using the following
command:
./run 1 Joiner default > results.dat
"run" is the program that I am
