Drool@cup.portal.com (Paul James Coene) (12/14/89)
shell302a users: I am using shell302a and am getting little response from the two folks in Italy when I direct questions there. I wonder if anyone could help with a problem I am having... I have immense problems piping one shell script into a second script which uses pipes internally. Consider the following shell302a scripts: ----snip----snip----snip----snip----snip----snip----snip----snip----snip scripta: echo bob stanley echo rich walton echo goose gossage echo bob allen scriptb: cat >ram:bah forline i ram:bah "echo $i | input a;echo $a" ----snip----snip----snip----snip----snip----snip----snip----snip----snip Before I explain, bear in mind these accomplish nothing in particular, besides illustrate a problem (in my mind) in shell302a. Running scripta produces the list of names, as one would expect. Redirecting a text file into scriptb via "scriptb <file" echos out the file as would be expected. Typing: shell -c "scripta" | shell -c "scriptb" produces a redirection error, within scriptb. I believe scriptb is trying to create a temporary pipe file with the same name as that used for the pipe between the scripts. My experiments lend data to this thoery. Other methods, such as scripta | scriptb which takes automatic sourcing for granted doesn't work at all, as the shell gets confused. SUMMARY! Does anyone have legally distributable source that I could modify, or better yet an alternative method to pipe between two shell302a scripts, where the latter uses pipes within? Or worse yet, maybe you have seen an error in my ways? <: Drool :> |----------------------------------| | There's so many different worlds | | There's so many different suns | | And we have just one world, | | But we live in different ones. | | | | - Dire Straits | |----------------------------------| Only IBM makes it Impossible ;) UUCP: kodak!bisco!retreat!drool ARPA: drool@cup.portal.com