Where has my output gone?

I run my ruby script, and it produces lots of output

I run the same script, but redirect the output to a file (bash shell using >),
no output!

Whats going on? I just know there is a simple answer, and I have a nagging
feeling that its been discussed here before...

Help...quick...please... before I pull _all_ my hair out!

TIA

Andrew Walrond

Is there any chance that your program is outputting to stderr instead of
stdout?

SteveT

Steve Litt

slitt@troubleshooters.com

···

On Friday 09 December 2005 08:09 am, Andrew Walrond wrote:

I run my ruby script, and it produces lots of output

I run the same script, but redirect the output to a file (bash shell using
>), no output!

Whats going on? I just know there is a simple answer, and I have a nagging
feeling that its been discussed here before...

Help...quick...please... before I pull _all_ my hair out!

TIA

Andrew Walrond

Andrew Walrond wrote:

I run my ruby script, and it produces lots of output

I run the same script, but redirect the output to a file (bash shell
using >), no output!

Whats going on? I just know there is a simple answer, and I have a
nagging feeling that its been discussed here before...

Help...quick...please... before I pull _all_ my hair out!

Did you wait until your script actually terminated? If not, you probably
became a victim of buffering. Try $stdout.sync=true or $>.sync=true at
the start of the script instead of pulling hair out.

Kind regards

    robert

Nope; example:

root@orac main $ sbin/heretix --bs /home/andrew/prebuild/x86_64/ --cf kdelibs version=none
Build settings: cpu=x86_64 build-jobs=4 make-jobs=4
Processing......
  -u kdelibs
  -u kdebase
root@orac main $ sbin/heretix --bs /home/andrew/prebuild/x86_64/ --cf kdelibs version=none > out
root@orac main $ cat out
root@orac main $

···

On Friday 09 December 2005 13:52, Steve Litt wrote:

Is there any chance that your program is outputting to stderr instead of
stdout?

Damn. I should have known that.

Thanks Robert!

Andrew Walrond

···

On Friday 09 December 2005 15:02, Robert Klemme wrote:

became a victim of buffering. Try $stdout.sync=true or $>.sync=true at
the start of the script instead of pulling hair out.