[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to deal with errors in <()?

From: Peng Yu
Subject: Re: How to deal with errors in <()?
Date: Mon, 9 Mar 2015 17:19:38 -0500

On Mon, Mar 9, 2015 at 2:07 PM, Chet Ramey <address@hidden> wrote:
> On 3/8/15 6:05 PM, Stephane Chazelas wrote:
>> Are bash questions no longer on topic here? bash-bug used to be
>> the place to discuss bash (before help-bash was created). It maps to the
>> gnu.bash.bug newsgroup. I don't think help-bash maps to usenet
>> (though you can access it over NNTP on gmane).
> I personally don't care which mailing list gets the questions.
>> $ bash --norc
>> bash-4.3$ echo <(exit 123)
>> /dev/fd/63
>> bash-4.3$ echo "$!"
>> 12142
>> bash-4.3$ wait "$!"
>> bash: wait: pid 12142 is not a child of this shell
>> Having the process substitution pid in $! is not very useful if
>> you can't wait for it to retrieve the status.
> I agree.  I will look at making that work for the next release of bash.

Would making an environment array (just as PIPE_STATUS) that will be
expanded to the process IDs of the all executed background commands
started from the last command be helpful to my original question? (But
this should also work with commands connected by pipes in order to
solve the problem.)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]