SRFERGU@ERENJ.BITNET (Scott Ferguson) (12/23/89)
In the past, I learned that since Aegis shells ran "inprocess", you couldn't
multitask/concurrently run processes by piping output of one into input of
another. For example, you have a front-end program with a user interface that
formats commands for a package with a command line-based input language.
You'd do this:
% front_end : big_program
I found from the vast knowledge base known as apollo@umix.cc.umich.edu that
UNIX DOES allow this by spawning a process for each program in the pipeline.
Well, I tried the same tactic with a twist, and am having trouble. Let's say,
you'd like to pipe standard output of one program into input of a program on a
remote, non-Apollo machine, say an Ardent.
I figured that you just say:
% front_end : rsh remotehost 'big_program'
When I do this, however, the stdout of the front-end doesn't reach stdin
in the remote shell until the front-end exits, just like an Aegis shell would.
Why would an rsh run in-process, or is it something else?
Of course, I chose to do this because mbx_$ system calls are not part of UNIX,
and my Ardent is UNIX. Now, you're asking, why not use NCS, SYS5 Streams, or
other IPC implementation? Because I'm stuck at 9.7, and may be stuck there
for some time. I hesitate to get too deeply involved in things that have a
large number of problems fixed at sr10.
Thanks for any advice, and Happy Holidays.
Scott Ferguson
srfergu@erenj.bitnet
"That's no fuzzy dufflebag, that's my daughter, Fuzzy-Mae"