Re: Bash problem
joe_at_invalid.address
Date: 06/23/04
- Next message: Chuck: "Trapping SIGCHLD"
- Previous message: Alan Connor: "Re: Splitting output to two files"
- In reply to: Tim Pailthorpe: "Re: Bash problem"
- Next in thread: P.T. Breuer: "Re: Bash problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 23 Jun 2004 16:19:41 GMT
"Tim Pailthorpe" <pissofffilthyspammers@twats.***.com> writes:
> I am rellay confused now. Not by the solution but by who is
> suggesting what.
>
> For the sake of clarity...
>
> The example where I use more file |& is an example. What I am trying
> to do is more complicated. I am communicating interactively with
> Netcat using 2 way pipe so I can send raw email files to a mail
> relay bypassing MX records and other rules.
>
> I am happy to use ksh as that serves my purposes.
>
> Academically I wanted to know how this is acheived in bash. The
> documentation and howtos I have found on t'internet suggest that
> bash will also use the |& syntax. It doesn't seem to.
No, it doesn't. I've seen a few web pages that say bash will do
coprocesses as well, but if you try the sample scripts they don't
work. Neither is there anything about coprocesses in the bash man
page.
> Heiner's suggestion of named pipes is exactly the answer I wanted
> for future reference.
The bash distribution comes with a sample script that gives an example
of using fifos to achieve this functionality. On my linux box it's
/usr/share/doc/bash-2.05b/functions/coproc.bash
> I am guessing though that there is no similar command to |& in
> bash. Or am I wrong there?
No, you're correct.
Joe
-- Folks who don't know why America is the Land of Promise should be here during an election campaign. -- Milton Berle
- Next message: Chuck: "Trapping SIGCHLD"
- Previous message: Alan Connor: "Re: Splitting output to two files"
- In reply to: Tim Pailthorpe: "Re: Bash problem"
- Next in thread: P.T. Breuer: "Re: Bash problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]