I had the impression sed wasn't blocking, because when I do say:
iostat | sed
sed
processes the data as it arrives, but when I do
iostat | sed | netcat
Then sed
blocks netcat
.
Am I right?
I had the impression sed wasn't blocking, because when I do say:
iostat | sed
sed
processes the data as it arrives, but when I do
iostat | sed | netcat
Then sed
blocks netcat
.
Am I right?
sed
will work in buffered mode when it doesn't print to a terminal. This means that it will try to fill its internal buffer before doing any processing and output by default.
This is done to increase throughput, because normally in a pipe you don't care about the timing, but want as much data processed in a given time as possible.
Passing -u
to sed will tell it to work unbuffered, therefore working the same way it works when output goes to a terminal.
-u
is missing, but -l
works for line-buffering, which is preferred. –
Landes -u
but the results were the same: buffered. –
Antigua In addition to what @saua says, sed
is at least line oriented, that it, it read a line, then operates on it so it will always be buffering at least one line. In addition, sed
can work in multiline mode. If you are using a multiline pattern, then sed
can't output it's current buffer until it knows that the pattern either doesn't apply or the pattern has been processed.
I don't know if I understand the question right, but in your example, it should be like this:
Other than that, sed shouldn't need to read all its input to produce output.
Do you observe any delays that cannot be explained by this and some small buffering?
stdbuf
can assist with changing the buffering behavior of the standard io streams. You can try this to change the buffering behavior:
... | stdbuf -oL -eL sed -e ... | ...
© 2022 - 2024 — McMap. All rights reserved.