Re: Playing with pipes
- From: "P. Sture" <paul.sture.nospam@xxxxxxxxxx>
- Date: Tue, 05 Aug 2008 12:20:34 +0200
In article <slrng9elma.ouv.eric@xxxxxxxxxxxxxxxxxxxxxxx>,
Eric Junkermann <eric@xxxxxxxxxxxxxxxxx> wrote:
On 2008-08-04, JF Mezei <jfmezei.spamnot@xxxxxxxxxxxxx> wrote:
If I do this:
pipe myprog sys$output | rsh unixbox "cat - > xxxx"
I get the two lots of output mixed in file xxxx on the unixbox.
myprog would have to write its messages to another file. You could fopen
"TT:" for instance, and fprintf to it instead of doing printf. Then, you
could redefine TT to point to some logfile instead of a terminal, and
then the above command would work because only the binary data would be
sent to sys$output.
Darn, shouln't have called it "myprog", because it isn't mine, and I
can't do that.
Also, you might want to use SYS$PIPE which is the official "pipe".
(sys$output gets redirected to sys$pipe).
Tried that (I think - too many possible combinations), but I need to
send what should be sys$output somewhere else, and what should be a
named file to sys$output, and do both of these at once. :(
It could be that the program concerned doesn't honour SYS$OUTPUT
properly. One notable example of this was the help in UCX 3.n, where I
ended up extracting the text from the help library, as from the program
prompt it scrolled off the top of a VT screen.
You could try TT: just in case that has been hard-coded.
- Prev by Date: Re: Monitor Utility
- Next by Date: Tin-Men (was: Re: Show of support for Distributed NetBeans)
- Previous by thread: Re: Playing with pipes
- Next by thread: RE: Playing with pipes