On 9/11/18 4:46 PM, Robert Elz wrote:
> If it is unspecified, then a script cannot start an async pipeline,
> then want to run another while the first is executing, with a
> different pipefail setting (different to that for the first) as as soon as
> the pipefail option is changed while the async pipelline is still
> running we get unspecified results from its status. That is a poor
> outcome, and really, needless. If the second pipeline were also
> async, then we end up with a real mess...
The chance of this happening in the future, when it has not happened
so far, is vanishingly small.
> So, why not try changing it (without announcing any change) in
> the alpha (or is it beta yet?) version of bash-5 - all of us here
> will promise not to tell the "real" users, or complain about it, and
> just see if there is anyone who notices. If you get complaints,
> you can always change it back, if all your users are happy (ie:
> they never even notice) then we will all be happy too!
We'll see how it goes. It took a #define and three lines of code.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
