4 ms·
> - splitting pipes to separate flows (e.g one flow for stderr, one for stdout). Think of it as a graph. Could you elaborate a little on what you mean by this?
by Splognosticus 6y ago
> - splitting pipes to separate flows (e.g one flow for stderr, one for stdout). Think of it as a graph.
Could you elaborate a little on what you mean by this? bash already has the ability to redirect STDERR and STDOUT independently, and when you introduce named pipes into the mix things can get really fancy (probably too fancy, this is about where your script stops being a script and starts being a program written in perhaps the most inconvenient language available.)
- e12e 6y agoI imagine an easy/intuitive way to set up FIFOs for stdout/stderr with redirection, maybe? A way to say: for this following section, I want stderr to go trough "|sort -n|logger -t DEBUG -f -" and standard out to go through (... Other pipeline)?
- folmar 6y agocommand 2> >(sort -n|logger -t DEBUG -f -) | other pipeline