bash coproc and leftover coproc output

Question

I need to read some configuration data into environment variables in a bash script.

The "obvious" (but incorrect) pattern is:

egrep "pattern" config-file.cfg | read VAR1 VAR2 VAR3 etc...

This fails because the read is run in a subshell and therefore cannot set variables in the invoking shell. So I came up with this as an alternative

coproc egrep "pattern" config-file.cfg
read -u ${COPROC[0]} VAR1 VAR2 VAR3 etc...

which works fine.

To test what happens if the coprocess returns more than one line, I tried this:

coproc cat config-file.cfg
read -u ${COPROC[0]} VAR1 VAR2 VAR3 etc...

where config-file.cfg contains three lines.

$ cat config-file.cfg
LINE1 A1 B1 C1
LINE2 A2 B2 C2
LINE3 A3 B3 C3

I expected this to process the first line in the file, followed by some kind of "broken pipe" error message. While it did process the first line, there was no error message and no coprocess was left running.

So I then tried the following in a script:

$ cat test.sh
coproc cat config-file.cfg
read -u ${COPROC[0]} VAR1 VAR2 VAR3 VAR4
echo $VAR1 $VAR2 $VAR3 $VAR4
wait
echo $?

Running it:

$ bash -x test.sh
+ read -u 63 VAR1 VAR2 VAR3 VAR4
+ cat config-file.cfg
LINE1 A1 B1 C1
+ wait
+ echo 0
0

Where did the remaining two lines go? I would have expected either "broken pipe", or the wait to hang since there was nothing to read the remaining lines, but as you can see the return code was zero.

Answer 1

As per comments above, you can use process substitution to achieve just that. This way, read is not run in a subshell and the captured vars will be available within the current shell.

read VAR1 VAR2 VAR3 < <(egrep "pattern" config-file.cfg)

---

"If the <(list) form is used, the file passed as an argument should be read to obtain the output of list" -- what "file passed as an agrument" are they talking about?

That is rather cryptic to me too. The chapter on process substitution in Advanced Bash-scripting Guide has a more comprehensive explanation.

The way I see it, when the <(cmd) syntax is used, the ouput of cmd is made available via a named pipe (or temp file) and the syntax is replaced by the filename of the pipe/file. So for the example above, it would end up being equivalent to:

read VAR1 VAR2 VAR3 < /dev/fd/63

where /dev/fd/63 is the named pipe connected to the stdout of cmd.